This chapter describes ELS post-installation tasks. The following topics are included:
Before proceeding, verify that you have completed the installation tasks described in "Installing ELS Software"
There are no specific post-installation tasks for VTCS. Refer to the ELS publication Configuring HSC and VTCS for required VTCS configuration tasks.
SMC, HSC, and VTCS must run as authorized programs in MSP. Therefore, you must perform the following steps to APF authorize the ELS load library:
Add the ELS load library to the KAAAPFzz member of SYS1.PARMLIB.
Issue the commands described in "Authorizing the ELS Load Library" to authorize the load library.
Add the following entry to the KAAAPFzz member to authorize the ELS load library:
your.SEALINK volser,
Before adding this entry to your authorized program list, edit the high level qualifier and volser with appropriate values for your system.
If there are multiple entries in the KAAAPFzz member, each entry (except the last) must end with a comma to indicate continuation. Omit the comma on the last entry.
Note:
If the ELS load library resides on an SMS-managed volume, you do not need to specify a volume in the authorized library entry. In this case, specify nothing after the library name, to indicate that SMS is managing the library. If you specify the wrong volume, the library cannot be authorized.Adding an entry to the KAAAPFzz member is necessary so that the library will be authorized in event of an IPL.
In the meantime, dynamically authorize the library on your running system by issuing one of the following MSP system commands:
If the library is SMS managed, issue the following command:
SETPROG APF,ADD,DSN=your.SEALINK,SMS
If the library is not SMS managed, issue the following command:
SETPROG APF,ADD,DSN=your.SEALINK,volser
Edit the high level qualifier and volser with appropriate values for your system.
This section describes required SMC post-installation tasks. The following topics are included:
SMC executes as a dynamically defined MSP subsystem. It can either run under the master MSP subsystem, or as a secondary subsystem under the primary Job Entry Subsystem.
Because SMC is dynamically defined, for many installations, it does not need to be added to the MSP subsystem name table.
However, under any of the following conditions, you must add SMC to the MSP subsystem name table (SYS1.PARMLIB member SUBSYSzz) as required.
If you run SMC and the Unicenter CA-MIA product on the same host, add both Unicenter CA-MIA and the SMC to the subsystem name table to ensure the correct order of EDL processing. See "Unicenter CA-MIA Interaction and the Subsystem Name Table."
If you run SMC, a tape management system, and the Unicenter CA-MIA product on the same host, add all three products to the subsystem name table. See "SMC, TMS, and Unicenter CA-MIA Interaction and the Subsystem Name Table."
To run the SMC under the master MSP subsystem (rather than under the primary Job Entry Subsystem), add the SMC to the subsystem name table. See "Running SMC under MSTR and the Subsystem Name Table."
In addition, the PROCLIB containing the SMC START procedure must be present in the PROCLIB concatenation for the master address space. This concatenation is defined in SYS1.PARMLIB(MSTJCLzz), under DD IEFPDSI.
If you run a Tape Management System (TMS), you must ensure that it processes MSP mount messages before the SMC. Add both the tape management system and the SMC to the subsystem name table with the (TMS) entry preceding the SMC entry. The following example shows entries for CA-1 Release 5.1 and above, and SMC.
SUBSYS SUBNAME(JES) PRIMARY(YES) START(NO) SUBSYS SUBNAME(TMS) SUBSYS SUBNAME(SMC0) INITRTN (SMCBPREI)
In installations with tape management systems executing on the same host, it is recommended that you always add both the tape management system and the SMC to the subsystem name table.
The following are possible subsystem name definition scenarios for a tape management system and SMC when both are dynamic subsystems:
Scenario 1
In this scenario, both SMC and the TMS are defined in the subsystem name table. This scenario is supported and recommended. The TMS must precede the SMC in the table.
Scenario 2
In this scenario, SMC is defined in the subsystem name table, while the TMS is not. This scenario is not supported. The TMS cannot process MSP mount messages before the SMC.
Scenario 3
In this scenario, the TMS is defined in the subsystem name table, while SMC is not. This scenario is supported but not recommended. You must ensure that the SMC is started after the TMS.
If you run the Unicenter CA-MIA product, Computer Associates recommends that you add both SMC and Unicenter CA-MIA to the subsystem name table with the SMC entry preceding the entry for Unicenter CA-MIA.
The following example shows entries for SMC and Unicenter CA-MIA:
SUBSYS SUBNAME(JES) PRIMARY(YES) START(NO) SUBSYS SUBNAME(SMC0) INITRTN(SMCBPREI) SUBSYS SUBNAME(MIA)
Unicenter CA-MIA compatibility also requires that the ALLOCDEF MIACOMPAT(ON) option be specified in SMC. Refer to the ELS Command, Control Statement, and Utility Reference for information about the ALLOCDEF command.
If you run SMC, a Tape Management System (TMS), and Unicenter CA-MIA all on the same host, add all three products to the subsystem name table in the order indicated in the following example:
SUBSYS SUBNAME(JES) PRIMARY(YES) START(NO) SUBSYS SUBNAME(TMS) SUBSYS SUBNAME(SMC0) INITRTN(SMCBPREI) SUBSYS SUBNAME(MIA)
Unicenter CA-MIA compatibility also requires that the ALLOCDEF MIACOMPAT(ON) option be specified in SMC. Refer to the ELS Command, Control Statement, and Utility Reference for information about the ALLOCDEF command.
To run the SMC under the MSTR subsystem rather than under the primary Job Entry Subsystem, you must add the following entry to the subsystem name table to identify the SMC subsystem name:
SUBSYS SUBNAME(SMC0)
If your primary Job Entry Subsystem is JES, then the SMC cannot run under MSTR, but must be executed under JES.
If the SMC subsystem is to execute under MSTR, you must also include the MSTR option on the PARM parameter in the SMC START procedure. Refer to the ELS publication Configuring and Managing SMC for information about creating the SMC START procedure.
An alternative to adding the SMC to the subsystem name table to execute under MSTR is to start the SMC subsystem with the SUB=MSTR parameter on the MSP Start command. Refer to the ELS publication Configuring and Managing SMC for information about executing the SMC start procedure.
If you choose to modify the subsystem name table for SMC, use the following guidelines:
The SUBNAME(name) parameter specifies a 1-4 character name that corresponds to the SMC START procedure name. If the SMC subsystem name you define using the SUBNAME(name) parameter does not match the SMC START procedure name, you must include the SYSS option on the PARM parameter in the START procedure. Refer to the ELS publication Configuring and Managing SMC for information about creating the SMC START procedure.
You must use the keyword format of the SUBSYS command rather than the positional format. Refer to your Fujitsu MSP/EX publications for more information about defining subsystem names.
If you are not defining the subsystem name dynamically, you must perform an IPL of the MSP host system before the SMC subsystem name entry takes effect.
If you have added the Unicenter CA-MIA subsystem name to the subsystem name table, one of the following is required:
The started task that uses this subsystem must be present in the PROCLIB concatenation for the master address space. This concatenation is defined in SYS1.PARMLIB(MSTJCLzz), under DD IEFPDSI.
The Start command for Unicenter CA-MIA must specify the SUB=JES parameter.
For example, S CAMIA,SUB=JES.
You must modify the MSP Program Properties Table (PPT) to include an entry for the SMC subsystem.
Add the following entry to member PPTPRMzz of SYS1.PARMLIB:
PPT PGMNAME(SMCBINT),PRIV,SYST,KEY(3)
Note:
The SMC must run in a low key (from 1-7). The examples in this section use key 3. Using keys 8-15 causes unpredictable results.
After modifying the PPTPRMzz member, you must perform an IPL or dynamic update.
SMC uses a data space with SCOPE=COMMON to perform its inter-address space communications.
This section describes required HSC post-installation tasks. The following topics are included:
HSC can either run under the master MSP subsystem, or as a secondary subsystem under the primary Job Entry Subsystem.
If you run HSC under the master MSP subsystem, you must add a line to your subsystem name table (SYS1.PARMLIB member SUBSYSzz) to identify the subsystem name. This is a one- to four-character name that corresponds to the procedure name for the HSC started task procedure.
If you run HSC as a secondary MSP subsystem, you must add a line to your subsystem name table (SYS1.PARMLIB member SUBSYSzz) to identify the following:
The subsystem name. This is a one- to four-character name that corresponds to the HSC START procedure name.
The HSC subsystem initialization routine name, which must be SLSBPREI.
Assuming your HSC subsystem name is SLS0, the following lines correctly add HSC to your subsystem name table when running HSC under the master MSP subsystem, or as a secondary MSP subsystem:
SUBSYS SUBNAME(SLS0) /* keyword format */
Note:
If the HSC subsystem name you define in the subsystem name table does not match the HSC START procedure name, you must include the SYSS option on the PARM parameter in the START procedure. Refer to the ELS publication Configuring HSC and VTCS for information about creating an HSC startup procedure.
HSC no longer interacts with tape management systems in processing MSP messages. Therefore, the order of definition of the HSC subsystem and a tape management subsystem is irrelevant. However, the SMC subsystem definition, if specified, must follow the tape management system entry.
Refer to your Fujitsu MSP/EX publications for more information about defining subsystem names.
The HSC user exit library can either be the same as the HSC load library, or a separate library. If the HSC user exit library is a separate library, you must perform the following steps to APF authorize the user exit load library:
Add the HSC user exit load library to either the KAAAPFzz member of SYS1.PARMLIB.
Issue the commands described in "Authorizing the HSC User Exit Load Library" to authorize the load library.
Add the following entries to the KAAAPFzz member to authorize the HSC user exit load library:
your.SEALINK volser your.HSC_USEREXIT.LOAD volser
Before adding these entries to your authorized program list, edit the high level qualifier and volser with appropriate values for your system.
If there are multiple entries in the KAAAPFzz member, each entry (except the last) must end with a comma to indicate continuation. Omit the comma on the last entry.
Note:
If the HSC user exit load library resides on an SMS-managed volume, you do not need to specify a volume in the authorized library entry. In this case, specify nothing after the library name, to indicate that SMS is managing the library. If you specify the wrong volume, the library cannot be authorized.Adding an entry to the KAAAPFzz member is necessary so that the library will be authorized in event of an IPL. In the meantime, dynamically authorize the library on your running system by issuing one of the following MSP system commands:
If the library is SMS managed:
SETPROG APF,ADD,DSN=your.HSC_USEREXIT.LOAD,SMS
If the library is not SMS managed:
SETPROG APF,ADD,DSN=your.HSC_USEREXIT.LOAD,volser
In both commands, edit the high level qualifier and volser with appropriate values for your system.
The HSC subsystem pre-initialization routine module (SLSBPREI), which resides in the SEALINK library, must also reside in an MSP LINKLIST library if you run the HSC as a secondary MSP subsystem. You can copy or move the SLSBPREI module from SEALINK to a LINKLIST library.
The SLSBPREI pre-initialization routine module is functionally compatible between HSC releases. For future compatibility, however, use the most current release of the SLSBPREI pre-initialization module.
You must modify the MSP Program Properties Table (PPT) to include an entry for the HSC subsystem.
Add the following entry to member PPTPRMzz of SYS1.PARMLIB:
PPT PGMNAME(SLSBINIT),PRIV,SYST,KEY(3)
Note:
The HSC must run in a low key (from 1-7). The examples in this section use key 3. Using keys 8-15 causes unpredictable results includingSOC1 and SOC4 abends.HSC can produce SMF record subtypes for HSC and VTCS events. To produce these record subtypes, you must add two lines to your System Management Facility (SMF) parameters in SYS1.PARMLIB member SMFPRMzz to specify the following:
HSC subsystem name
HSC recording interval, specified as INTERVAL(hhmmss).
The smaller the number, the more often data is recorded.
A minimum of 15 minutes (001500) is strongly recommended to avoid impacts to library performance. For HSC systems that do not support VSM, an interval of one hour (010000) is recommended.
HSC SMF record type
HSC/VTCS SMF record subtypes to be recorded.
Refer to the ELS Programming Reference for more information about the subtypes that HSC and VTCS can generate.
Assuming your HSC subsystem name is SLS0, the following example shows the lines that add HSC and VTCS record subtypes:
SUBSYS(SLS0,INTERVAL(001500),TYPE(255))SUBPARM(SLS0(SUBTYPE,(1-8,10,11,13,14,15,16,17,18,19,20,21,25,26,27,28,29,30,31)))
Note:
If you do not specify theSUBTYPE parameter in your SMF options, HSC generates subtypes 1 through 6. You must code a SUBPARM parameter and include subtypes 7 and 8 to generate cartridge move and view records.Depending on your tape management system and its associated release level, you may need to re-assemble the TMS (Tape Management System) interface (SLUDR*) routines called by the HSC SLUCONDB utility and SMC SMCUDBX utility. This is also necessary if local modifications are made to these routines. These routines are included in the SEALINK library generated during ELS installation.
Note:
The source of the TMS interface routines changed for ELS 7.0. If you have local modifications to any module with a name matching SLUDR*, you must modify the ELS 7.0/7.1/7.2/7.3 source with your local changes and re-assemble. Older versions of the SLUDR* modules are not compatible with the ELS 7.0/7.1/7.2/7.3 versions of SLUCONDB.
Refer to the ELS Command, Control Statement, and Utility Reference for more information about the SLUCONDB and SMCUDBX utilities, and the TMS interface routines.
Refer to the ELS publication Managing HSC and VTCS for more information about Scratch Conversion (SLUCONDB) utility re-assembly requirements.