System Startup, Configuration, and Shutdown Reference Manual > Chapter 8 Modifying System File Configurations

Entering the SYSFILE Configurator

	MPE documents
	Complete PDF
	Table of Contents
	Glossary
	Index

	E0802 Edition 7
	E0201 Edition 6 ♥
	E0796 Edition 5

Example 8-1 demonstrates activating the SYSFILE configurator. To access the SYSFILE configurator, enter the SYSFILE command (abbreviated SY) at the SYSGEN prompt:

Example 8-1 Activating the SYSFILE Configurator


   sysgen>SY

          ** SYSFILE configurator commands **

          aauto (aa)      aboot (ab)     acmsl (ac)     asprog (as)
          cmsl (cm)       dauto (da)     dboot (db)     dcmsl (dc)
          dsprog (ds)     lcmsl (lc)     rauto (ra)     rboot (rb)
          rcat (rc)       rcmsl (rcm)    rdcc (rd)      ripl (ri)
          rnmlib (rn)     rsprog (rs)    show (sh)

          clear (cl)(c)   exit (ex)(e)   help (he)(h)   hold (ho)

For additional information on entering the SYSFILE configurator, refer to Chapter 4 "Using the System Generator (SYSGEN)"

Using the SYSFILE Configurator Help Facility

The help facility enables you to identify quickly the function and syntax of SYSFILE configurator commands and options.

The help facility operates similarly to the global help facility. Example 8-2 demonstrates using the SYSFILE configurator's help facility to list all available SYSFILE commands. To obtain the list of commands, enter HELP at the SYSFILE configurator prompt:

Example 8-2 SYSFILE Configurator HELP


   sysfile>HELP

          ** SYSFILE configurator commands **

          aauto (aa)      aboot (ab)     acmsl (ac)     asprog (as)
          cmsl (cm)       dauto (da)     dboot (db)     dcmsl (dc)
          dsprog (ds)     lcmsl (lc)     rauto (ra)     rboot (rb)
          rcat (rc)       rcmsl (rcm)    rdcc (rd)      ripl (ri)
          rnmlib (rn)     rsprog (rs)    show (sh)

          clear (cl)(c)   exit (ex)(e)   help (he)(h)   hold (ho)

Example 8-3 demonstrates using the SYSFILE configurator's help facility for listing all SYSFILE commands and their syntax. To display the syntax for each available command at the current level, enter HELP ALL.

Example 8-3 SYSFILE Configurator HELP ALL


  sysfile>HELP ALL

        commands (abb)  parameter=value
        --------------  ---------------
        aauto (aa)      file      = filename
                        type      = DISC|TAPE|BOTH
        aboot (ab)      image     = boot image name
                        file      = filename
                        type      = DISC|TAPE|BOTH
        acmsl (ac)      seg       = segment-name
                        file      = filename
                        [mode     = S|C|P|U]
        asprog (as)     prog      = program-name
                        file      = filename
        cmsl (cm)       [sl       = sl-name]
        dauto (da)      type      = DISC|TAPE|BOTH
        dboot (db)      image     = boot-image-name,...
        dcmsl (dc)      seg       = segment-name,...
        dsprog (ds)     prog      = program-name,...
        lcmsl (lc)      [seg      = segment-name]
        rauto (ra)      file      = autoboot filename
                        type      = DISC|TAPE|BOTH
        rboot (rb)      image     = boot-image-name
                        file      = filename
                        type      = DISC|TAPE|BOTH
        rcat (rc)       name      = filename
        rcmsl (rcm)     seg       = segment-name
                        file      = filename
                        [mode     = S|C|P|U]
        rdcc (rd)       file      = filename
        ripl (ri)       image     = IPL image name
                        file      = IPL file name
                        type      = DISC|TAPE|BOTH
        rnmlib (rn)     file      = filename
        rsprog (rs)     prog      = program-name
                        file      = filename
        show (sh)       [file     = AUTO|BOOT|CATALOG|CMSL|DCC|IPL
                                    NMLIB|SPROG|ALL]
                        [dest     = OFFLINE]

To request help for a specific SYSFILE configurator command, enter HELP commandname at the SYSFILE configurator prompt. as shown in Example 8-4.

Example 8-4 SYSFILE Configurator HELP ABOOT


   sysfile>HELP ABOOT

           aboot (ab)     image     = boot image name
                          file      = filename
                          type      = DISC|TAPE|BOTH
   sysfile>

Using SYSFILE Configurator Commands

The SYSFILE configurator commands perform five actions (add, delete, replace, list, and specify) on eight objects (autoboot image, boot image, compatibility mode segmented library (CMSL), system program, system catalog, network configuration (NETWORK CONFIG), initial program loader (IPL) image, and native mode library (NM LIBRARY)). In addition, the SYSFILE configurator provides other commands, some of which are common to other SYSGEN configurators: CLEAR, EXIT, HELP, HOLD, OCLOSE, and the colon (:).

Table 8-1 "SYSFILE Configurator Command Matrix" shows a command matrix of the add, delete, replace, list, and specify commands. The objects are listed from top to bottom, and the actions are listed from left to right.

Table 8-1 SYSFILE Configurator Command Matrix

	ADD	DELETE	REPLACE	LIST	SPECIFY
AUTO BOOT IMAGE	AAUTO	DAUTO	RAUTO
BOOT IMAGE	ABOOT	DBOOT	RBOOT
CM SL SEGMENT	ACMSL	DCMSL	RCMSL	LCMSL	CMSL
SYSTEM PROGRAM	ASPROG	DSPROG	RSPROG
SYSTEM CATALOG			RCAT
NETWORK CONFIG			RDCC
IPL IMAGE			RIPL
NM LIBRARY			RNMLIB

All commands have a two- or three-character abbreviation.

CAUTION: Do not use the SYSFILE> RSPROG command to rename Hewlett-Packard supplied MPE/iX HP e3000 system files. A renamed system file can corrupt your system during an update. This problem can occur if you have third party software installed on your system and you have renamed some system files to use this software.

Use the SHOW command in SYSFILE to ensure that all Hewlett-Packard supplied system files have retained their original name. System filenames in both columns should be identical. If they are not identical, rename the files in the second column to the filename in the first column.

NOTE: The examples used to demonstrate SYSFILE configurator commands may produce display screens that do not exactly match output from your system. What SYSGEN displays depends entirely on how your system is configured.

Displaying Current File Information

The SHOW command (abbreviated SH) displays the file information currently set through SYSFILE. SHOW has the following parameters:


   SHOW (SH)   [FILE =  AUTO    ]
                      [ BOOT    ]
                      [ CATALOG ]
                      [ CMSL    ]
                      [ DCC     ]
                      [ IPL     ]
                      [ NMLIB   ]
                      [ SPROG   ]
                      [ ALL     ]
               [DEST =  OFFLINE ]

AUTO shows all the autoboot images.

BOOT shows all the boot images currently configured.

CATALOG shows the system catalog in use.

CMSL shows the CMSL (compatibility mode segmented library) in use.

DCC shows which file will be used for network configuration.

IPL shows the IPL images in use.

NMLIB shows the NM library names.

SPROG shows the specified system program names.

ALL shows all of the above information.

OFFLINE redirects the output of the SHOW command to SYSGEN's listing file, SYSGLIST. Using OFFLINE does not immediately generate a printout. The information is sent to SYSGLIST until you either enter the OCLOSE command or exit SYSGEN. Exiting SYSGEN or using OCLOSE closes SYSGLIST and prints the file.

To see current file information, enter the SHOW command and at least one parameter:


   sysfile>SH NMLIB

   NM LIB      = NL.PUB.SYS

To show all the current system file information for system libraries, programs and the message catalog, enter SHOW ALL or SHOW as shown in Example 8-5.

Example 8-5 SYSFILE Configurator SHOW ALL Output


 sysfile>SHOW ALL

           DISC AUTOBOOT  = NONE
           TAPE AUTOBOOT  = NONE
           SYSTEM CATALOG = CATALOG.PUB.SYS
           CM SL          = SL.PUB.SYS
           NMCONFIG FILE  = NONE
           NM LIB         = NL.PUB.SYS

   BOOT FILE                  FILENAME                         TYPE
   ---------                  --------                         ----
   ISL.MPEXL.SYS              ISL.MPEXL.SYS               disc boot
   DUMP.MPEXL.SYS             DUMP.MPEXL.SYS              disc boot
   START.MPEXL.SYS            START.MPEXL.SYS             disc boot
   INSTALL.MPEXL.SYS          INSTALL.MPEXL.SYS           tape boot
   UPDATE.MPEXL.SYS           UPDATE.MPEXL.SYS            tape boot
   A1002AI.MPEXL.SYS          A1002AI.MPEXL.SYS           both boot
   A1002AM.MPEXL.SYS          A1002AM.MPEXL.SYS           both boot
   A1002AP.MPEXL.SYS          A1002AP.MPEXL.SYS           both boot
   A1100AI.MPEXL.SYS          A1100AI.MPEXL.SYS           both boot
   A1100AM.MPEXL.SYS          A1100AM.MPEXL.SYS           both boot
   A1100AP.MPEXL.SYS          A1100AP.MPEXL.SYS           both boot
   CAEXR.MPEXL.SYS            CAEXR.MPEXL.SYS             both boot
   IOMAP.MPEXL.SYS            IOMAP.MPEXL.SYS             both boot
   CLKUTIL.MPEXL.SYS          CLKUTIL.MPEXL.SYS           both boot
   DISCUTIL.MPEXL.SYS         DISCUTIL.MPEXL.SYS          both boot
   SADPATCH.MPEXL.SYS         SADPATCH.MPEXL.SYS          both boot
   SAT.MPEXL.SYS              SAT.MPEXL.SYS               both boot
   MPROC.MPEXL.SYS            MPROC.MPEXL.SYS             both boot
   UNIPROC.MPEXL.SYS          UNIPROC.MPEXL.SYS           both boot
   MDIAG.MPEXL.SYS            MDIAG.MPEXL.SYS             both boot
   TDIAG.MPEXL.SYS            TDIAG.MPEXL.SYS             both boot
   EDBC.MPEXL.SYS             EDBC.MPEXL.SYS              both boot
   EDPROC.MPEXL.SYS           EDPROC.MPEXL.SYS            both boot

   IPL FILE                   FILENAME                         TYPE
   ---------                  --------                         ----
   ISL2.MPEXL.SYS             ISL2.MPEXL.SYS               tape ipl
   MMSAVE.MPEXL.SYS           MMSAVE.MPEXL.SYS             disc ipl

   SYSTEM PROGRAM             FILENAME                         TYPE
   --------------             --------                         ----
   IFHPIBFS.PUB.SYS           IFHPIBFS.PUB.SYS          system prog
   XL.PUB.SYS                 XL.PUB.SYS                system prog
   PSIMDBDL.DIAG.SYS          PSIMDBDL.DIAG.SYS         system prog
   PSINIODL.DIAG.SYS          PSINIODL.DIAG.SYS         system prog
   SYSDIAG.PUB.SYS            SYSDIAG.PUB.SYS           system prog
         .                          .                         .
         .                          .                         .
   DTCSWI04.PUB.SYS           DTCSWI04.PUB.SYS          system prog
   DTCSWJ04.PUB.SYS           DTCSWJ04.PUB.SYS          system prog
   DTCSWK04.PUB.SYS           DTCSWK04.PUB.SYS          system prog
   DTCSWL04.PUB.SYS           DTCSWL04.PUB.SYS          system prog
   DTCSWM04.PUB.SYS           DTCSWM04.PUB.SYS          system prog

The add commands (AAUTO, ABOOT, ACMSL, and ASPROG) add objects to the list of files dumped onto SYSGEN's tape:

AAUTO adds an autoboot file to the list of files.

ABOOT adds a boot image to the list of files.

ACMSL adds a segment to a temporary copy of the CMSL, which SYSGEN automatically manages.

ASPROG adds a system program or other file to the list of files.

Adding Autoboot Files

The AAUTO command (abbreviated AA) adds an autoboot file to the list of files dumped onto SYSGEN's tape. The command has the following parameters:


   AAUTO (AA)  [FILE     =]  autobootfilename
               [TYPE     =   DISC ]
                           [ TAPE ]
                           [ BOTH ]

FILE specifies the file name that contains autoboot commands. If it is not fully qualified with group and account name, it defaults to the current group and account. If the specified file does not exist, an error occurs, and the system issues a message.

NOTE: Always use fully qualified file names.

TYPE specifies the type of autoboot files to add. TYPE allows the following types:

DISC: Specifies that the file is applicable to a disk boot only.
TAPE: Specifies that the file is applicable to a tape boot only.
BOTH: Specifies that the file is applicable to both disk boot and tape boot.

There can be only one disk and one tape autoboot file, although neither is required. The tape and disk autoboot files become TAPEAUTO.MPEXL.SYS and AUTOBOOT.MPEXL.SYS, respectively.

Adding Boot Files

The ABOOT command (abbreviated AB) adds a boot image to the system file configuration. The command has the following parameters:


   ABOOT (AB)  [IMAGE     =] bootimagename
               [FILE      =] filename
               [TYPE      =  DISC ]
                           [ TAPE ]
                           [ BOTH ]

IMAGE specifies the name of a boot image. If the specified boot image already exists, an error occurs.

FILE adds the file name of the boot image. If the file name is not fully qualified, it defaults to the current group and account. If SYSGEN is run from a different group and account when the tape is made, unexpected results occur (for example, cannot find the specified files). If the file to be added does not exist, an error occurs.

TYPE specifies the type of boot images to add. TYPE allows the following types:

DISC: Specifies that the file is applicable to a disk boot only.
TAPE: Specifies that the file is applicable to a tape boot only.
BOTH: Specifies that the file is applicable to both disk boot and tape boot.

To add file information for the boot image, enter the ABOOT command, file name, and at least one parameter:


   sysfile>ABOOT START2.UTIL.SYS START2.UTIL.SYS TYPE=DISC

Adding a Segment to the Compatibility Mode Segmented Library (CMSL)

The ACMSL command (abbreviated AC) adds a segment to the CMSL. The command has the following parameters:


   ACMSL (AC)  [SEG  =]  segmentname
               [FILE =]  filename
               [MODE =   S ]
                       [ C ]
                       [ P ]
                       [ U ]

SEG specifies a new segment name with a maximum of eight characters. If an existing segmentname is specified, an error occurs.

FILE specifies a file name to be added to the CMSL. The filename parameter can be fully qualified with group and account. If not, it defaults to the current group and account. If filename cannot be found, an error occurs.

MODE indicates where the added SL segment is to reside. It expects one of the four options listed below. Other entries cause errors.

P: Declares a segment to be a permanently allocated user segment. This parameter performs the same function as the ALLOCATE command.
S: Declares a segment to be a permanently allocated system intrinsic segment (in virtual memory).
C: Declares a segment to be a core-resident system intrinsic segment.
U: Declares a segment to be a temporarily allocated user segment.

Adding File Names to Dump to Tape

The ASPROG command (abbreviated AS) adds a system program or other file to the list of files to be saved on tape. The command has the following parameters:


   ASPROG (AS)   [PROG     =] program-name
                 [FILE     =] filename

PROG expects a system program name. If the specified program-name already exists in the system program list, an error occurs.

FILE expects a file name to be used as the system program. If it is not fully qualified with group and account name, it defaults to the current group and account. If the specified filename does not exist, an error occurs.

To add a program to tape, enter the program and file name:


   sysfile>ASPROG FCOPY.PUB.SYS FCOPY.PUB.SYS

Deleting Objects from the SYSGEN Tape

The delete commands (DAUTO, DBOOT, DCMSL, and DSPROG) delete objects from the list of files dumped to tape with SYSGEN's global module TAPE command:

DAUTO deletes the specified autoboot type from the list of files.

DBOOT deletes boot images from the list of files.

DCMSL deletes segments from the CMSL.

DSPROG removes system programs or files from the configuration.

Deleting Autoboot Images

The DAUTO command (abbreviated DA) deletes the specified autoboot type from the list of files dumped onto SYSGEN's tape. The command has the following parameter:


   DAUTO    [TYPE  =   DISC ]
                     [ TAPE ]
                     [ BOTH ]

TYPE specifies the type of autoboot file deleted. The following types are allowed:

DISC: Specifies that the file applies to disk only.
TAPE: Specifies that the file applies to tape only.
BOTH: Specifies that the file applies to both disk and tape.

Deleting an autoboot file, creating a SYSGEN tape, and updating your system using the newly generated tape does not remove the disk autoboot file from the system. Remove the disk file using the ISL INSTALL command.

Deleting Boot Images

The DBOOT command (abbreviated DB) deletes a boot image file name. If the boot image has an associated library, DBOOT also deletes the library. DBOOT has the following parameter:


   DBOOT (DB)     [IMAGE     =] bootimagename

IMAGE is a repeated parameter that specifies which boot image names you want to delete. If a specified boot image name does not exist in the configuration, a warning is issued.

Use the SHOW command to display a listing of the applicable boot image file names.

To delete one or more boot image file names, enter DBOOT and the file name(s) to be removed at the SYSFILE prompt:


   sysfile>DBOOT filename

Deleting Compatibility Mode Segments from a SYSGEN Tape

The DCMSL command (abbreviated DC) deletes segments from the compatibility mode segmented library (CMSL). The DCMSL command has the following parameter:


   DCMSL (DC)     [SEG     =] segment-name,...

SEG is a repeated parameter that specifies the existing segment name. If a nonexistent segment name is specified, an error occurs.

Use the LCMSL command to list the contents of the CMSL.

Removing System Programs from a SYSGEN Tape

The DSPROG command (abbreviated DS) removes system programs or files from the system configuration. DSPROG has the following parameter:


   DSPROG (DS)     [PROG     =] programname,...

PROG is a repeated parameter that specifies the system program name to be deleted. If a specified program name does not exist, an error occurs.

To remove a program or file name, enter the command and name:


   sysfile>DS FCOPY.PUB.SYS

Deleting a system program does not remove it from the disk. To remove it from disk, an ISL INSTALL must be performed.

Replacing Objects on the SYSGEN Tape

The replace commands (RAUTO, RBOOT, RCAT, RCMSL, RDCC, RIPL, RNMLIB, and RSPROG) replace or modify information in the list of SYSGEN dump files.

RAUTO replaces an existing autoboot image or modifies the autoboot type.

RBOOT replaces an existing boot image or modifies the boot type.

RCAT replaces the message catalog.

RCMSL replaces a segment in the temporary copy of the CMSL.

RDCC replaces network configuration file dumped to the SYSGEN tape.

RIPL replaces an existing IPL image.

RNMLIB replaces a native mode (NM) library.

RSPROG replaces an existing system program or other file.

Replacing Autoboot Images

The RAUTO command (abbreviated RA) replaces an existing autoboot image in the list of files dumped to SYSGEN's tape. The command has the following parameters:


   RAUTO (RA)   [FILE  =]  autobootfilename]
                [TYPE  =   DISC  ]
                         [ TAPE  ]
                         [ BOTH  ]

FILE specifies a file name to replace the designated autoboot image. If it is not fully qualified with group and account name, it defaults to the current group and account. If the specified file does not exist, an error occurs.

TYPE specifies the boot image type. The various types are defined as follows:

DISC: Specifies that the file is applicable to a disk boot only.
TAPE: Specifies that the file is applicable to a tape boot only.
BOTH: Specifies that the file is applicable to both disk boot and tape boot.

To modify or replace an autoboot image file name, enter the command, fully qualified file name, and type:


   sysfile>RAUTO filename TYPE=DISC

Use the SHOW command to display the autoboot image file names maintained by the system.

Replacing Boot Images

The RBOOT command (abbreviated RB) modifies the boot type of an existing boot image file name or replaces the boot image file name with another boot image file name. The command has the following parameters:


   RBOOT (RB)  [IMAGE  =]  boot-image-name
               [FILE   =]  filename
               [TYPE   =   DISC  ]
                          [ TAPE ]
                          [ BOTH ]

IMAGE specifies an existing boot image name to be modified or replaced. If the specified boot image does not exist, an error occurs.

FILE specifies a file name to replace the designated boot image. If it is not fully qualified with group and account name, it defaults to the current group and account. If the specified file does not exist, an error occurs.

TYPE specifies the boot image type. The various types are defined as follows:

DISC: Specifies that the file is applicable to a disk boot only.
TAPE: Specifies that the file is applicable to a tape boot only.
BOTH: Specifies that the file is applicable to both disk boot and tape boot.

To modify or replace a boot image file name, enter the command, image name, and fully qualified file name. Here are two examples.


   sysfile>RBOOT imagename TYPE=DISC

   sysfile>RBOOT imagename filename DISC

Use the SHOW command to display the boot image file names maintained by the system.

Configuring a Message Catalog

The RCAT command (abbreviated RC) configures the message catalog to be used on the target system. RCAT has the following parameter:


   RCAT (RC)     [NAME     =] filename

The system message catalog contains all the system and subsystem messages. It is retained under a known file name (CATALOG.PUB.SYS).

NAME specifies a catalog file name. If the name is not fully qualified, it defaults to the current group and account.

To replace the default catalog name CATALOG.PUB.SYS with a new catalog name, enter RCAT and the fully qualified file name:


   sysfile>RCAT filename.group.account

If the new message catalog file was not previously created, an error occurs.

NOTE: For information on how to modify an existing message catalog, refer to the Message Catalogs Programmer's Guide.

Replacing a CMSL Segment

The RCMSL command (abbreviated RCM) replaces a segment in the CMSL. RCMSL has the following parameters:


   RCMSL (RCM)  [SEG  =] segment-name
                [FILE =] filename
                [MODE =   S ]
                        [ C ]
                        [ P ]
                        [ U ]

SEG specifies a new segment name of maximum eight characters. If a nonexistent segment name is specified, an error occurs.

MODE indicates where the added SL segment is to reside. It expects one of the four options listed below. Other input causes an error.

P: Declares a segment to be a permanently allocated user segment. This parameter performs the same function as the ALLOCATE command.
S: Declares a segment to be a permanently allocated system intrinsic segment (in virtual memory).
C: Declares a segment to be a core-resident system intrinsic segment.
U: Defaults if MODE is not specified.

Use the LCMSL command to display the segments maintained in the CMSL.

Replacing or Defining a Network Configuration File

The RDCC command (abbreviated RD) defines the network configuration file to be used. This command also checks for conflicts with SYSGEN's I/O configuration. The file named becomes NMCONFIG.PUB.SYS for SYSGEN's tape only. The user must install or update the system from tape before the file can be used by the network software.

RDCC has the following parameter:


   RDCC (RD)     [FILE     =] filename

The FILE parameter identifies the network configuration file. If the name is not fully qualified, it defaults to the current group and account. If no file parameter is entered, the network configuration file is changed back to NMCONFIG.PUB.SYS.

To add the network configuration file information to the current SYSGEN configuration information, enter the command and file name. Then, follow this sample sequence:


   sysfile>RDCC filename.group.account
   sysfile>HOLD          (Cross-validation conflicts noted)
   sysfile>EXIT
   sysgen>IO            (Make I/O changes if necessary)
                           (Conflicts also noted here)
   sysgen>KEEP NETWORK  (Conflicts also noted here)
   sysgen>TAPE          (Conflicts also noted here)

For additional information, refer to Chapter 5 "Modifying Input/Output (I/O) Configurations" For additional information on remote configurations, refer to the Asynchronous Serial Communications System Administrator's Reference Manual and the HP 3000/iX Network Planning and Configuration Guide.

Replacing an IPL Image

The RIPL command (abbreviated RI) replaces an existing IPL image in the list of files dumped onto SYSGEN's tape. The command has the following parameters:


   RIPL (RI) [IMAGE =]imagename [FILE =]filename

IMAGE specifies an existing IPL image to be modified or replaced. If the specified image does not exist, an error occurs and the system issues a message.

FILE specifies a file name to replace the specified IPL image. If it is not fully qualified with group and account name, it defaults to the current group and account. If the specified file does not exist, an error occurs and the system issues a message.

There can be only one disk and one tape IPL, each of which is replaced by its image name. Both IPL files must reside on the tape.

To replace an IPL image, enter the command and the image and file names:


   sysfile>RIPL imagename filename

Replacing the Native Mode Library

The RNMLIB command (abbreviated RN) replaces the system NM library that resides in NL.PUB.SYS. The RNMLIB command has the following parameters:


   RNMLIB (RN) [FILE =]filename

FILE is the file name of the library to replace the current one. If the file name is not fully qualified, it defaults to the current group and account. If the file name does not exist, an error occurs.

To replace an existing NM library, enter the following command format:


   sysfile>RNMLIB filename.group.account

Replacing a System Program

The RSPROG command (abbreviated RS) replaces an existing system program. RSPROG has the following parameters:


   RSPROG (RS) [PROG =]programname [FILE =]filename

PROG specifies an existing program name. If the name entered does not exist, an error occurs.

FILE specifies the file name to replace the specified system program. If the file name is not fully qualified with group and account name, it defaults to the current group and account. If the file name does not exist, an error occurs.

Enter the command, an existing program name, and the fully qualified file name to replace the system program:


  sysfile>RSPROG programname.group.account filename.group.account

Use the SHOW command (SH SPROG) to display all the system programs maintained by the configuration.

Using a Segmented Library File as CMSL

The CMSL command (abbreviated CM) specifies an SL file to be used as the compatibility mode SL. CMSL has the following parameter:


   CMSL (CM) [SL =] slname

The slname parameter is an SL file name. If the SL file name is not fully qualified, it defaults to the current group and account. If an SL name is not specified, the default is SL.PUB.SYS.

Enter the command and a fully qualified SL name to change the default, SL.PUB.SYS, as shown in the following example.


   sysfile>CMSL NEWSL.PUB.SYS

Listing CMSL Contents

The LCMSL command (abbreviated LC) lists the contents of the CMSL or a single segment in the CMSL. LCMSL has the following parameter:


   LCMSL (LC) [SEG =] segmentname

The segment name designates which segment to list. If the segment name is not specified, the entire contents of the CMSL is listed.

If SYSGEN cannot locate the segment name, an error is generated, and the command is rejected by the segmenter.

To list the contents of a single segment, enter the command and the segment name:


   sysfile>LCMSL cminin

To list the entire CMSL, enter the command without a parameter.

NOTE: The LCMSL command locks whichever SL it is listing. If the CMSL is SL.PUB.SYS, and no changes have been made (changes force a temporary SL to be created), any program that uses the SL stops. This can cause the system to appear to be down.

Clearing SYSFILE Configurator Changes

If you desire to clear all SYSFILE configuration changes made, enter the CLEAR command at the SYSFILE configurator prompt:


   sysfile>CLEAR

Once a SYSGEN> KEEP is done, the changes become permanent and CLEAR does not remove them.

Holding and Saving Configuration Changes

Using the SYSFILE configurator commands described in the previous sections changes the configuration specified in the SYSGEN command line or global BASEGROUP command. These changes are temporary and are lost if not properly saved.

Saving configuration changes is a two-step procedure. After you alter a configuration, you must first, hold the changes before exiting the configurator. Second, use the global module KEEP command to save the changes.

To hold changes, enter the HOLD command (abbreviated HO) at the SYSFILE configurator prompt:


   sysfile>HOLD

You can work in a SYSGEN configurator, hold the changes, and continue working in another SYSGEN configurator before saving the changes.

To save the changes, hold all desired changes, exit to SYSGEN's global module, and issue the KEEP command (abbreviated KE or K):


   sysgen>KEEP newgroupname

Entering an MPE Command from the SYSFILE Configurator

Use the colon (:) to introduce an MPE command while in the SYSFILE configurator. To issue an MPE command, enter the command following the colon. For example:


   sysfile>:SHOWTIME

   THU, APR 20, 1989, 2:55PM

   sysfile>

Exiting the SYSFILE Configurator

Use the EXIT command (abbreviated EX or E) to deactivate the SYSFILE configurator and to return to the SYSGEN global module.

To exit the configurator, enter EXIT at the SYSFILE configurator prompt:


   sysfile>EXIT
   sysgen>

Chapter 8 Modifying System File Configurations

Chapter 9 Halting System Activity