If you are a new customer, you have to start HSC. If you are an existing customer doing an upgrade and all of your configuration changes are non-disruptive, you will not have to restart HSC.
Note:
SMC now supports the z/OS reusable ASID feature, which requires that you do the following:Update DIAGxx member in SYS1.PARMLIB with REUSASID(YES)
On the start command add REUSASID=YES: S SMC,REUSASID=YES,
To start HSC:
Ensure that you have completed ELS installation and configuration as described in Installing ELS and Configuring HSC and VTCS.
Modify your HSC start-up JCL procedure as required. For more information, see "Creating and Cataloging the HSC Startup Procedure."
Enter the MVS START command to run HSC startup procedure. For example:
S SLSO
If your CDS configuration contains VTCS configuration data, VTCS starts automatically unless you specify the startup parameter NOVTCS (for more information, see "Creating and Cataloging the HSC Startup Procedure." For more information on startup scenarios, see "HSC Startup Scenarios."
Note:
If your SMF options for HSC did not specify the SUBTYPE parameter, HSC issues a message that SMF record subtypes 1 through 6 are being recorded.
If you did not specify GTF EID and FID parameters on the PARM operand in HSC start procedure, HSC issues a message indicating that default EID and FID values are being used.
HSC can be started prior to hardware arrival to make sure that it has been installed properly. HSC subsystem comes up with the LMU stations offline. HSC operator commands may be entered but any functions requiring interaction with the ACS hardware result in error messages.
Alternately, a JCL substitution symbol may be specified in HSC cataloged procedure, and additional parameters passed using the START command using the substitution symbol.
HSC can be initialized to a full or base service level by issuing the MVS START command. HSC can also be preinitialized or initialized under the MVS Master subsystem (MSTR) through the START command.
In a multiple-host configuration, start one host at a time. Do not bring up multiple hosts simultaneously.
Start SMC. For more information, refer to Configuring and Managing SMC.
If necessary, do post-startup tasks. These are required only when the CDS is first initialized:
All LSMs are offline, so vary them online with HSC MODify ONline. For subsequent executions of HSC, the last recorded status of the LSMs is obtained from the CDS.
All CAP preferences are zero (never selected), so use the CAPPREF command to set CAP preferences.
Table 7-1 shows examples of the START command options, which are further described in the following sections.
| HSC Started Under: | HSC Start Command: | Proc Name Same as IEFSSNxx Entry? | SLSBPREI in IEFSSNxx or Previous HSC Start With PARM='INIT'? |
|---|---|---|---|
|
MSTR and PROC in SYS1.PROCLIB |
S SLS0 S SLS0,SUB=MSTR S SLS0,PARM='SSYS(SLS0)', SUB=MSTR |
Yes Yes No |
No Ignored Ignored |
|
JES and PROC in Any PROCLIB |
S SLS0 S SLS0,PARM='INIT' S SLS0,PARM='SSYS(SLS0)' S SLS0,PARM='INIT,SSYS(SLS0)' S SLS0,PARM='SSYS(SLS0)' |
Yes Yes No No No |
Yes No Yes No No |
A system IPL is required after defining HSC as a subsystem using the Subsystem Name Table entry IEFSSNxx for the first time. Once HSC has been defined, you do not need to re-IPL to stop and start HSC. If you are migrating from a previous HSC release and HSC is defined in the IEFSSNxx member, then a system IPL is not required. You must perform a COLD start at the first HSC startup. Subsequent HSC startups should not require a COLD start unless a problem is encountered.
If you are using SLSBPREI to initialize HSC under JES, see "Preinitializing HSC as an MVS Subsystem" for additional information about starting HSC.
If you are not using SLSBPREI, refer to "Starting HSC with PARM=’INIT'" and "Initializing HSC Under the Master Subsystem" for additional information about starting HSC without SLSBPREI.
HSC must be initialized as an MVS Subsystem. There are two ways to preinitialize HSC:
specifying SLSBPREI as HSC subsystem initialization routine in the IEFSSNxx member of the system PARMLIB and IPLing MVS as follows:
SUBSYS SUBNAME(SLS0) INITRTN(SLSBPREI) /* keyword format */
Note:
SLSBPREI must reside in SYS1.LINKLIB or its link list. After installation, copy the SLSBPREI module from HSC SEALINK to a library in the MVS link list.Instead of using SLSBPREI for HSC subsystem initialization routine, you can specify PARM='INIT' in a START command for a preinitialization startup followed by a START command for the actual startup of HSC. This eliminates the need for HSC's subsystem Master Scheduler Initialization (MSI) routine. MSI functions are taken over by the main HSC address space initialization routines. The use of any subsystem MSI exit routine imposes a restriction that it must be in a data set that is cataloged in the master catalog, and included in the linklist. Previous HSC versions have distributed this module to install in SYS1.LINKLIB. This preinitialization of HSC is for initializing HSC under the primary Job Entry Subsystem (JES).
For example, to preinitialize HSC:
S SLS0,PARM='INIT'
To then start HSC:
S SLS0
If you want to initialize HSC under the Master subsystem (MSTR), consider the following:
If SLSBPREI is not part of the subsystem definition in IEFSSNxx or a previous initialization of the subsystem occurred using the INIT parameter, then enter the following to start HSC under Master subsystem control:
S SLS0,SUB=MSTR
If SLSBPREI is not part of the subsystem definition in IEFSSNxx and the subsystem name is the same as the startup procedure name, then no preinitialization or SUB=MSTR is necessary:
S SLS0
If you want to initialize HSC under JES later, you can use the INIT parameter to preinitialize HSC.
When running HSC under the Master subsystem, JES services are not used. It is also possible to receive duplicate messages in the system log.
If the EXEC statement PARM parameter specifies a subsystem, you can start HSC as a subsystem. For more information, see "EXEC Statement." For example:
S SLS0,PARM='SSYS(SLS0)'
To start HSC at Full Service Level:
S SLS0
To start HSC at Base Service Level:
S SLS0,PARM='BASE'
The BASE parameter should be used with other parameters in the START command since these parameters override whatever is specified in HSC START Procedure. A sample START command with parameters is:
S SLS0,PARM='BASE E(086) F(23) M(00) SSYS(SLS0)'
For a partitioned SL8500 and SL3000 libraries, NCO will automatically be invoked at HSC startup. This must be done for HSC to update these libraries' configuration for HSC to operate properly. Below is an example of new messages seen during HSC startup:
SLS0054I ACS 00 now ONLINE SLS0668I LSM 00:00 IS OFFLINE; TEMP OUTAGE QUEUE HAS BEEN PURGED. SLS0054I ACS 01 now ONLINE SLS0668I LSM 01:00 IS OFFLINE; TEMP OUTAGE QUEUE HAS BEEN PURGED. SLS2256I Automatic CAP Service AVAILABLE SLS1505I HSC service level FULL initialization complete SLS4459I Library configuration changes started SLS0668I LSM 01:01 IS OFFLINE; TEMP OUTAGE QUEUE HAS BEEN PURGED. SLS0668I LSM 01:02 IS OFFLINE; TEMP OUTAGE QUEUE HAS BEEN PURGED. SLS0668I LSM 01:03 IS OFFLINE; TEMP OUTAGE QUEUE HAS BEEN PURGED. SLS4400I HSC dynamic reconfiguration initiated SLS4402I CDS drive record not found for existing transport; id = 00:00:10:00 SLS4402I CDS drive record not found for existing transport; id = 00:00:10:02 SLS4405D CDS / LMU conflicts exist; allow dynamic reconfig to proceed; Reply 'Y' or 'N' SLS4419I CAP 00:00:01 status changed from UNALLOCATED to OFFLINE SLS4419I CAP 00:00:03 status changed from UNALLOCATED to OFFLINE SLS4419I CAP 00:00:04 status changed from UNALLOCATED to OFFLINE SLS4414I Initial configuration for LSM 00:00, total cells 2,710, free cells 2,710 SLS4407I HSC dynamic reconfiguration processing has ended. SLS4460I Library configuration changes complete on ECCL SLS4459I Library configuration changes started SLS4400I HSC dynamic reconfiguration initiated SLS4402I CDS drive record not found for existing transport; id = 01:00:01:00 SLS4402I CDS drive record not found for existing transport; id = 01:00:01:01 SLS4402I CDS drive record not found for existing transport; id = 01:00:01:02 SLS4402I CDS drive record not found for existing transport; id = 01:00:01:03 SLS4405D CDS / LMU conflicts exist; allow dynamic reconfig to proceed; Reply 'Y' or 'N' SLS4401I LSM/Rail 01:02 successfully unallocated from current HSC configuration SLS4401I LSM/Rail 01:03 successfully unallocated from current HSC configuration SLS4407I HSC dynamic reconfiguration processing has ended. SLS4460I Library configuration changes complete on ECCL
During HSC initialization, HSC remains active if LSM or panel type configuration mismatches occur between the CDS and LMU. Specifically, these mismatches include different:
Numbers of LSMs
Or unknown types of LSMs
Or unknown panel types in an LSM.
In these cases, the affected ACS(s) are forced offline. HSC continues to support the unaffected ACS(s), and you can correct the configuration problems and bring the affected ACSs back online.
You can stop HSC in either of two ways:
By first quiescing HSC, which you do with the MVS STOP command, where:
HSC waits for pending work to complete. This includes actions against the LMU such as current mounts and dismounts, utilities, active CAPs, operator commands, and station termination(s).
HSC updates the CDS and journals as pending work completes.
HSC cleans up resources, terminates, and displays a termination message on the system console.
By forcing HSC termination with the MVS Cancel command. If this does not stop HSC, enter another Cancel command. If this does not work, use the MVS FORCE command.
Caution:
Oracle does not recommend forced termination of HSC because unpredictable results may occur on startups following forced terminations.A forced termination of HSC causes all HSC processes to abort immediately and termination occurs. Any of the following can occur:
Volumes can be left in-transit, however, mounted volumes are not affected by forced HSC termination.
Outstanding utilities can abend.
The CDS and journals can lose synchronization.
If you do choose to force HSC termination:
Before forcing termination, verify that alternative library paths exist for the active SMC to continue performing allocation influencing and mount automation.
Errant volume records are created for volumes left in the playground, CAPs, or passthru ports. Operator intervention may be required to resolve the status of errant volumes when HSC execution is resumed. Transports may require operator intervention to satisfy mount requests.