Working with subsystem records (SSYS)

If authorization for a database fails and you list the database and all the subsystem records in the RECON data set, you might wonder how the subsystem names (SSIDs) were created.

The following list discusses different aspects of the SSIDs.

• Naming conventions for SSIDs in RECON subsystem records

  The SSYS record is created when a signon call is issued to DBRC. The SSID must be unique. Normal conventions for creating the subsystem name are:

    IMS and DBCTL subsystems = IMSID value from IMSCTRL SYSGEN macro
                               (four characters)
   
    BATCH and UTILITY SUBSYSTEMS = JOBNAME
   
    XRF = RSENAME (Recovery Service Element) of the IMS systems
          (active and alternate)
   

  Exceptions include the following:

   ONLINE IMAGE COPY - XXXTZZZZ where
   
           XXXT is the DMB number of the database + DCB number translated 
           to 0-9,A-Z
           ZZZZ is the control region IMSID
   

  Online image copy is the only BMP that creates its own subsystem record in the RECON data set.

• Batch backout

  If batch backout is processing a log created by a batch subsystem, the SSID that is used is the job name of the subsystem that is being backed out. The job name of the batch backout utility job is not used.

  If batch backout is processing a log that was created by an online subsystem, the job name of the backout utility job is used as the SSID.

• Deleting a subsystem record

  When you no longer need a particular subsystem record in the RECON data set, the following commands can be used to delete the SSYS:

       CHANGE.SUBSYS SSID(XXXXX) STARTRCV
       CHANGE.SUBSYS SSID(XXXXX) ENDRECOV  <---(removes auth from DB)
       DELETE.SUBSYS SSID(XXXXX)
   

• Subsystem record size

  The subsystem record grows in size. If the subsystem record grows to exceed the 16M maximum record size, IMS abends.