S36E: Using a Library in an IASP with the System/36 Environment

Resolving The Problem

A work management enhancement allows a S36E user to use a library that resides on an Independent ASP (IASP) as their S36E configured default files library.

Note: QS36F is the shipped default files library name; however, the S36E configured default files library name can be changed to be any library name by using the CHGS36 or CHGS36A CL commands.

When using the work management enhancement to allow their S36E configured default files library to reside on an IASP, a S36E customer must take into account the following considerations:

1.	Because the controlling subsystem is not allowed to use an IASP for the subsystem monitor job, a S36E-configured default files library will still be created in *SYSBAS whenever the system is IPLed and the controlling subsystem is started. This configured default files library, created in *SYSBAS by the controlling subsystem monitor job, must be deleted before the IASP that contains the true S36E-configured default files library is varied on.
2.	Any subsystems to be made "S36E-capable" when they are started must be updated with the ASPGRP parameter as described below. They must be started after the IASP that contains the true S36E-configured default files library that is varied on and available for use.
3.	Jobs that run under a given subsystem that is using an IASP should also use that IASP (for example, the jobs should add that IASP to their name spaces). For a job to enter the S36E, that job must be able to find the configured default files library.

Subsystem monitor job changes
Use the ASPGRP parameter on the Create Subsystem Description (CRTSBSD) or Change Subsystem Description (CHGSBSD) command

In addition, you must ensure that the job descriptions, which the subsystem uses when creating user jobs, specify an Initial ASP Group (INLASPGRP) parameter that matches the ASPGRP parameter of the subsystem description. The ASP group for the user job overrides the ASP group of the subsystem.

Although the work management enhancement must be used to allow the S36E configured default files library to reside on an IASP, changing the S36E session files library or the S36E current files library values for their operating system jobs to use libraries that reside on IASPs does not require the work management enhancement. The FLIB procedure can be used to change the session files library value. The FILELIB OCL statement can be used to change the session or current files library values.

For files that reside in a files library on an IASP:

o	Authority holders cannot be created to define authorities to such files (for example, CRTAUTHLR restriction 4 states that Authority holders can only secure files in the system auxiliary storage pool (ASP) for a basic user ASP).
o	Deleted or scratched files are deleted entirely from the system rather than being placed in the S36E deleted file cache (for potential reuse).

In this example, subsystem MYQCMN will use the IASP group named IASPGRP1 and will cause subsystem MYSBSNAME to use the IASP group named IASPGRP2.

The IASP must be varied on and available before the subsystem is started.  The subsystem must be ended before the IASP is varied off.

Look at the subsystem monitor job's job log.  For example, if your subsystem is called "MYQCMN", you could issue the following command:

WRKACTJOB SBS(MYQCMN)

and then take Option 5 (Work with) on the line for the subsystem job, and then Option 10 (Display job log, if active or  on job queue). If the subsystem is using the ASP group, you will see a CPIB8EA message (ASP group set to ...) with the name of the ASP group.

The controlling subsystem is not allowed to use an IASP for  the subsystem monitor job.

If the system has more than one available IASP group and if jobs in the subsystem require access to more than one IASP group, this data area solution will not help and could interfere with normal IASP handling by the subsystem.

This function does not provide a way to change the library list for the subsystem monitor job.  The subsystem library specified on the Create Subsystem Description (CRTSBSD) command or specified on the Change Subsystem Description (CHGSBSD) command will not be found if the library is on the IASP.

Message CPD1681 will still be issued for various commands such as those that modify the subsystem description.  The message text states that active subsystems do not find objects that are in an independent ASP, some subsystems can find some objects that are in an independent IASP.

Note: In addition to the Subsystem description update, the following PTFs should be installed:

R610
SI39175
SI40863

R710
SI39347
SI42041