This chapter describes ELS post-installation tasks. The following topics are included:
Before proceeding, verify that you have completed the installation tasks. See "Installing ELS and Additional Software" for more information.
There are no specific post-installation tasks for VTCS. Refer to the publication Configuring HSC and VTCS for required VTCS configuration tasks.
SMC, HSC, and VTCS must run as authorized programs in MVS. Therefore, you must perform the following steps to APF authorize the ELS load library:
Add the ELS load library to either the IEAAPFzz or PROGzz 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 IEAAPFzz 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 IEAAPFzz 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.Add the following entry to the PROGzz member to authorize the ELS load library:
APF ADD
DSNAME(your.SEALINK)
VOLUME(volser) | SMS
Before adding this entry to your authorized program list, edit the high level qualifier and volser with appropriate values for your system.
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 the literal SMS 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 IEAAPFzz or PROGzz members 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 MVS 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 MVS subsystem. It can either run under the master MVS 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 MVS subsystem name table.
However, under any of the following conditions, you must add SMC to the MVS subsystem name table (SYS1.PARMLIB member IEFSSNzz) as required.
If you run SMC and a tape management system on the same host, and the tape management system is also executing as an MVS dynamic subsystem, add both the tape management system and the SMC to the subsystem name table to ensure the correct order of message processing. See "Tape Management System Interaction and the Subsystem Name Table" for more information.
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" for more information.
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" for more information.
To run the SMC under the master MVS 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" for more information.
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 MVS 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(JES2) 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 MVS 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.
Note:
See "Notes on Subsystem Name Table Modifications for SMC" for more information.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(JES2) 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.
Note:
See "Notes on Subsystem Name Table Modifications for SMC" for more information.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(JES2) 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.
Note:
See "Notes on Subsystem Name Table Modifications for SMC" for more information.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 JES3, then the SMC cannot run under MSTR, but must be executed under JES3.
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 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 MVS Start command. Refer to the publication Configuring and Managing SMC for information about executing the SMC start procedure.
Consider the following:
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 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 IBM z/OS publications for additional information about defining subsystem names.
If you are not defining the subsystem name dynamically, you must perform an IPL of the MVS 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=JES2 parameter.
For example, S CAMIA,SUB=JES2.
The SMC subsystem pre-initialization routine module (SMCBPREI), which resides in the SEALINK library, must also reside in an MVS LINKLIST library if you run the SMC as a secondary MVS subsystem. You can copy or move the SMCBPREI module from SEALINK to a LINKLIST library.
The SMCBPREI pre-initialization routine module is functionally compatible between SMC releases. For future compatibility, however, use the most current release of the SMCBPREI pre-initialization module.
You must modify the MVS Program Properties Table (PPT) to include an entry for the SMC subsystem.
Add the following entry to member SCHEDzz 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 SCHEDzz member, you must perform an IPL or dynamic update.
SMC uses a data space with SCOPE=COMMON to perform its inter-address space communications. Ensure that the IEASYSzz member MAXCAD parameter is set appropriately in MVS to account for the SMC. This parameter controls the number of common data spaces that can be enabled on an MVS system.
For additional information, refer to your IBM z/OS publications.
This section describes required HSC post-installation tasks. The following topics are included:
HSC can either run under the master MVS subsystem, or as a secondary subsystem under the primary Job Entry Subsystem.
If you run HSC under the master MVS subsystem, you must add a line to your subsystem name table (SYS1.PARMLIB member IEFSSNzz) 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 MVS subsystem, you must add a line to your subsystem name table (SYS1.PARMLIB member IEFSSNzz) 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 MVS subsystem, or as a secondary MVS subsystem:
SUBSYS SUBNAME(SLS0) INITRTN(SLSBPREI) /* keyword format */
You can also define the HSC subsystem name dynamically using the MVS SETSSI command. For example:
If running under the master subsystem:
SETSSI ADD,SUB=SLS0
If running as a secondary subsystem:
SETSSI ADD,SUB=SLS0,INITRTN=SLSBPREI
In both examples, SLS0 is the HSC subsystem name, and SLSBPREI is the name of the HSC subsystem initialization routine.
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 publication Configuring HSC and VTCS for information about creating an HSC startup procedure.
If you are not defining the HSC subsystem name dynamically, you must perform an IPL of the MVS host system before the HSC subsystem name entry takes effect.
HSC no longer interacts with tape management systems in processing MVS 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.
HSC no longer interacts with tape management systems in processing MVS 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.
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 IEAAPFzz or PROGzz 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 IEAAPFzz 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 IEAAPFzz 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.Add the following entry to the PROGzz member to authorize the HSC user exit load library:
APF ADD
DSNAME(your.SEALINK)
VOLUME(volser) | SMS
APF ADD
DSNAME(your.HSC_USEREXIT.LOAD)
VOLUME(volser) | SMS
Before adding this entry to your authorized program list, edit the high level qualifier and volser with appropriate values for your system.
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 the literal SMS 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 IEAAPFzz or PROGzz members 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 MVS 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 MVS LINKLIST library if you run the HSC as a secondary MVS 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 MVS Program Properties Table (PPT) to include an entry for the HSC subsystem.
Add the following entry to member SCHEDzz 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.
INTERVAL is only valid for the following SMF subtype records:
BLOS (OSHDBLOS, x¿01¿)
LMU Read Statistics (OSHDLRST, x¿04¿)
HSC SMF record type
HSC/VTCS SMF record subtypes to be recorded.
Refer to the ELS Programming Reference for additional 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-21,25-33)))
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.The SMC Collector requires activation of a supplied SMF IEFU83/IEFU84 exit module. This module is installed using the z/OS Dynamic Exit Facility. To enable this facility, the SMF IEFU83 and IEFU84 exits must be specified in the SMFPRMxx PARMLIB member for SYS and SUBSYS(STC) entries. Review the SMF parameters to ensure the SMF IEFU83 and IEFU84 exits are specified.
SYS(.... EXITS(.... IEFU83,IEFU84 .....)) SUBSYS(STC,..... EXITS(... IEFU83,IEFU84 ....))
If HSC subsystems are defined with the IEFU83 and IEFU84 exits (both must be defined), these subsystems names must be included in the COLLECTOR SUBSYS parameter.The ORDER parameter (FIRST or LAST) on the COLlector command will be used to place the supplied exit module in that calling sequence if other IEFU83 and IEFU84 exits are installed.
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 additional information about the SLUCONDB and SMCUDBX utilities, and the TMS interface routines.
Refer to the publication Managing HSC and VTCS for additional information about Scratch Conversion (SLUCONDB) utility re-assembly requirements.
This section describes required post-installation tasks for JES3 environments with TAPE SETUP processing. The following topics are included:
"Creating and Installing the JES3 IATUX09 User Exit Modification for SMC"
"Creating and Installing the JES3 IATUX71 User Exit Modification for SMC"
If you installed the SMC JES3 support function with the ASSEM option, a link-edit and assembly of the SMCERSLV module was automatically performed. The SMCERSLV module obtains the correct offsets and lengths of the JES3 macro fields required by the SMC.
After the initial assembly and link-edit of the SMCERSLV module, you must manually reassemble this module each time IBM maintenance is applied to the JES3 macros. You can run member SMCJRSLV of the SMC SAMPLIB, causing a reassembly of SMCERSLV when certain JES3 macros are updated.
The SMCJRSLV library member is run against the MVS/JES3 target and distribution zones. Follow the instructions contained in the prologue of the SMCJRSLV job, make any necessary changes and run the job.
Note:
It is strongly recommended that you use theSMCJRSLV library member to reassemble the SMCERSLV module. Failure to reassemble the SMCERSLV module after applying maintenance to JES3 macros can result in unpredictable SMC operations.All load modules in the SMC JES3 load library must be accessible to the JES3 address space. Therefore, you must perform the following steps to APF authorize the SMC JES3 load library:
Add the SMC JES3 load library to either the IEAAPFzz or PROGzz member of SYS1.PARMLIB.
Issue the commands described in "Authorizing the SMC JES3 Load Library" to authorize the load library.
Note:
A JES3 ”hot start” is required to activate the modules listed above.
Module SMCERSLV must be accessible to the JES3 address space if the NOSMC parameter of the IATIIP1 Type 1 modification has been set to PROMPT. See "Creating and Installing SMC Type 1 Modifications" for more information about this modification.
Module SMCERSLV must be accessible to the SMC address space. This module is automatically assembled into the SMZLINK library where the SMZ7300 FMID is installed.
Add the following entry to the IEAAPFzz member to authorize the SMC JES3 load library:
your.SMZLINK volser,
Before adding this entry to your authorized program list, edit the high level qualifier and volser with the appropriate values for your system.
If there are multiple entries in the IEAAPFzz member, each entry (except the last) must end with a comma to indicate continuation. Omit the comma on the last entry.
Note:
If the SMC JES3 load library resides on an SMS-managed volume, you do not need to specify a volume in the authorized library entry. If you specify the wrong volume, the library cannot be authorized.Add the following entry to the PROGzz member to authorize the SMC JES3 load library:
APF ADD
DSNAME(your.SMZLINK)
VOLUME(volser)
Before adding this entry to your authorized program list, edit the high level qualifier and volser with the appropriate values for your system.
Note:
If the SMC JES3 load library resides on an SMS-managed volume, you do not need to specify a volume in the authorized library entry. If you specify the wrong volume, the library cannot be authorized.Adding an entry to the IEAAPFzz or PROGzz members 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 MVS system commands:
If the library is SMS managed:
SETPROG APF,ADD,DSN=your.SMZLINK,SMS
If the library is not SMS managed:
SETPROG APF,ADD,DSN=your.SMZLINK,volser
In both commands, edit the high level qualifier and volser with appropriate values for your system.
You must create and SMP/E install Type 1 modifications to certain JES3 modules for JES3 environments with TAPE SETUP processing.
Note:
If you plan to run the SMC on an MVS/JES3 system where HSC, MVS/CSC, or a prior release of SMC is currently running, you must remove the existing Type 1 modifications and create and install the SMC Type 1 modifications.Use the SMCEHOOK macro to create an SMC Type 1 modification for each of the following JES3 modules:
The type 1 modification to JES3 module IATIICM enables the SMC to retrieve DFSMS DATACLAS recording technique and media values when specified on the JCL DD statement. Install this modification only if your installation permits DATACLAS to be specified on JCL DD statements.
The type 1 modification to JES3 module IATIIP1 enables the SMC to perform device exclusion. The SMCEHOOK macro provides an ACALL in the IATIIP1 module that enables the SMC to determine where a data set's volume resides, and substitutes an esoteric name based on the volume's location in the job's intermediate job summary table (IJS). JES3 then creates a job summary table (JST) for the job that is used during device preferencing and volume fetch processing. This Type 1 modification is required.
Code the NOSMC parameter of the SMCEHOOK macro to indicate the action you want JES3 C/I to take if SMC is not active when C/I processing occurs. Choose the parameter value based on whether you want JES3 allocation to proceed if the SMC has not initialized. Valid values and actions include the following:
If NOSMC=PROMPT, one C/I process prompts the operator to start SMC and waits for SMC initialization.
If NOSMC=NONE, the C/I process continues with no StorageTek tape subsystem.
The type 1 modification to JES3 module IATMDAL enables the SMC to perform device preferencing. The SMCEHOOK macro provides an ACALL in the IATMDAL module that enables the SMC to direct the allocation of transports to the closest LSM containing the volume (specific requests), or to the LSM containing the largest number of scratch volumes (nonspecific requests). The JST created for the job is used during device preferencing and fetch processing. This Type 1 modification is required.
Code the TASKID parameter of the SMCEHOOK macro to indicate the task ID for device preferencing. The value must be between 151 and 255 inclusive. The default is 203.
The prologue for the SMCEHOOK macro provides detailed instructions regarding its use. The SMCEHOOK macro resides in the SMCMAC library.
SMC sample members SMCUIICM, SMCUIIP1, SMCUMDAL, and SMCUMDFE contain examples of the SMC JES3 Type 1 modifications.
After creating the SMC Type 1 modifications to the JES3 modules, you must SMP/E install the Type 1 modifications. Use the SMC SAMPLIB member SMCJTYP1 to SMP/E install the SMC Type 1 modifications for IATIICM, IATIIP1, IATMDAL, and IATMDFE. The following example shows the JCL included in the member SMCJTYP1:
//jobname JOB ..... //INSTTYP1 EXEC PGM=GIMSMP,REGION=4096K //SMPCSI DD DSN=your.jes3.global.csi,DISP=SHR //SMPPTFIN DD DSN=your.usermods,DISP=SHR //SMPHOLD DD DUMMY //SMPCNTL DD * SET BDY(GLOBAL). RECEIVE S( LUSIICM LUSIIP1 LUSMDAL LUSMDFE ) . SET BDY(jes3-target-zone) . APPLY S( LUSIICM LUSIIP1 LUSMDAL LUSMDFE ) . /*
Perform the following steps:
Allocate a new data set representing a working copy of your SMC SAMPLIB. Use your own naming conventions and specify the same LRECL, RECFM, and DSORG values as the original SMC SAMPLIB.
Note:
Do not edit your original SMCSAMPLIB.Copy SMC SAMPLIB members SMCUIIP1 and SMCUMDAL into the data set allocated in step 1. Perform the modifications documented at the top of both members.
Line numbering must be OFF when editing this data set, as described in steps 2-4.
Determine if the modification to IATIICM is appropriate for your system. If it is, copy the SMC SAMPLIB member SMCUIICM into the data set allocated in step 1. Perform the modification documented at the top of the member.
Determine if the modification to IATMDFE is appropriate for your system. If it is, copy the SMC SAMPLIB member SMCUMDFE into the data set allocated in step 1. Perform the modification documented at the top of the member.
Edit the SMC SAMPLIB member SMCJTYP1:
Change the JOB card to meet your local standards.
Change your.jes3.global.csi to the name of your JES3 global CSI.
Change your.usermods to the name of the data set allocated in step 1.
Change jes3-target-zone to the JES3 SMP/E target zone name.
If you have decided not to install the modification to IATIICM, remove LUSIICM from the RECEIVE and APPLY statements.
If you have decided not to install the modification to IATMDFE, remove LUSMDFE from the RECEIVE and APPLY statements.
Submit the job.
You must create and SMP/E install the JES3 IATUX09 user exit modification to enable deferred mounting and suppression of operator fetch messages for library volumes.
To defer mounts and suppress fetch messages for library volumes during common allocation, you must create the JES3 IATUX09 user exit source and user modification.
The JES3 IATUX09 user exit modification enables the suppression of operator fetch messages for library cartridge transports, and enables the deferred mount processing function. The use of this user exit is optional. However, it must be installed to defer mounts and suppress fetch messages for library volumes during common allocation.
If your installation already uses JES3 user exit IATUX09, rename the existing user exit and place your new load module name in the SETC's operand field at label ”&OLDUX09.” See the SETC at label ”&OLDUX09” in the sample user exit, SMC3UX09.
An example of the source is contained in SMC sample member SMC3UX09, and an example of the user modification is contained in SMC SAMPLIB member SMCUUX09.
After you create the JES3 IATUX09 user exit modification, you must SMP/E install the user exit modification. Use sample library member SMCJUX09 to SMP/E install the JES3 user exit modification.
The following example shows the JCL included in SMCJUX09:
//jobname JOB ..... //INSTUX09 EXEC PGM=GIMSMP,REGION=4096K //SMPCSI DD DSN=your.jes3.global.csi,DISP=SHR //SMPPTFIN DD DSN=your.usermods,DISP=SHR //SMPHOLD DD DUMMY //SMPCNTL DD * SET BDY(GLOBAL) . RECEIVE S( LUSUX09 ) . SET BDY(jes3-target-zone) . APPLY S( LUSUX09 ) . /*
Perform the following steps:
Allocate a new data set representing a working copy of your SMC SAMPLIB. Use your own naming conventions and specify the same LRECL, RECFM, and DSORG values as the original SMC SAMPLIB. If you previously allocated a data set as described in "Installing SMC Type 1 Modifications" you can use that data set.
Note:
Do not edit your original SMCSAMPLIB.Copy SMC SAMPLIB members SMCUUX09 and SMC3UX09 into the data set you allocated in step 1.
Examine the instructions documented at the top of SMCUUX09, and perform any necessary modifications.
Note:
If you are already usingIATUX09, you must rename the existing user exit modification.Edit the SMC SAMPLIB member SMCJUX09:
Change the JOB card to meet your local standards.
Change your.jes3.global.csi to the name of your JES3 global CSI.
Change your.usermods to the name of the data set you allocated in step 1.
Change jes3-target-zone to the JES3 SMP/E target zone name.
Submit the job.
You must create and SMP/E install the JES3 IATUX71 user exit modification to enable JES3 mount message (IAT5210) processing for library volumes.
To enable JES3 mount messaging processing for library volumes, you must create the JES3 IATUX71 user exit source and user modification.
The JES3 IATUX71 user exit modification enables the mounting of the required volume in response to JES3 mount message IAT5210. This user exit is optional. However, it must be installed to enable JES3 mount message processing for library volumes if the library subsystem policy requests no mount deferral. For HSC, no mount deferral is requested by setting the ALLOC command parameter DEFER to OFF. For MVS/CSC, no mount deferral is requested by setting the DEFER startup parameter to NO or by resetting its value to NO with an ALTER command.
An example of the user exit modification is contained in SMC sample member SMCUUX71.
After creating the JES3 IATUX71 user exit modification, you must SMP/E install the user exit modification. Use sample library member SMCJUX71 to SMP/E install the JES3 user exit modification.
The following example shows the JCL included in SMCJUX71:
//jobname JOB ..... //INSTUX71 EXEC PGM=GIMSMP,REGION=4096K //SMPCSI DD DSN=your.jes3.global.csi,DISP=SHR //SMPPTFIN DD DSN=your.usermods,DISP=SHR //SMPHOLD DD DUMMY //SMPCNTL DD * SET BDY(GLOBAL) . RECEIVE S( LUSUX71 ) . SET BDY(jes3-target-zone) . APPLY S( LUSUX71 ) . /*
Perform the following steps:
Allocate a new data set that will be a working copy of your SMC SAMPLIB. Allocate this data set as RECFM=FB, DSORG=PS, LRRECL=80, using your own data set naming conventions. If you previously allocated a set as described in "Installing SMC Type 1 Modifications" you can use that data set.
Note:
Do not edit your original SMCSAMPLIB.Copy SMC SAMPLIB members SMCUUX71 and SMC3UX71 into the data set you allocated in step 1. Follow the directions in "Creating and Installing the JES3 IATUX71 User Exit Modification for SMC" and then examine the instructions at the beginning of SMC3UX71 and perform any necessary modifications.
Note:
If you are already usingIATUX71, you must rename the existing user exit modification.Edit the SMC SAMPLIB member SMCJUX71:
Change the JOB card to meet your local standards.
Change your.jes3.global.csi to the name of your JES3 global CSI.
Change your.usermods to the name of the data set you allocated in step 1.
Change jes3-target-zone to the JES3 SMP/E target zone name.
Submit the job.