5. FILES › 5.2 Batch Information Area Files › 5.2.16 Multisystem Enclave Activity File (BATREN) › 5.2.16.3 BATREN Usage Considerations

5.2.16.3 BATREN Usage Considerations

Special considerations or techniques related to using the
BATREN file are provided below.
 
Read Section 6.12 for more information on multisystem
enclaves.
 
The most important thing to understand about multisystem
enclaves is that they execute on a system different from
the address space that is using them.  Because SYSID is
the highest or primary key on most CA MICS files, special
attention is needed for the SYSID on the BATREN file.
 
IBM does not provide the SYSID on the type 30 record within
each Multisystem Enclave Remote Data segment; however, the
system name is provided.  The system name can be used to
determine the value of the logical SYSID in the BATREN.  This
can be done by creating a FORMAT to map/cross-reference the
system name to the logical SYSIDs assigned in your CA MICS
databases.  The logical SYSID assignments are set up in the
sharedprefix.MICS.PARMS(CPLXSID) and
prefix.MICS.PARMS(SYSID). See sections 2.3.1.9 and 2.3.2.2 of
the PIOM for more information on logical SYSID.
 
SAS code has been developed for your use to build a format to
map the system name from the Multisystem Enclave Remote Data
Segment to the assigned logical SYSID. This code will read
one of the step-level files, depending on which type of
program activity is occurring.  The step-level files are:
 
o  BATPGM
o  BAT_TS
o  BAT_ST
o  BAT_TP
o  BAT_OE
o  BAT_SA
 
These files have both the SYSID and SYSNAME data elements.
The SYSID in the above mentioned files are mapped to the
logical SYSID assigned in either the
sharedprefix.MICS.PARMS(CPLXSID) or prefix.MICS.PARMS(SYSID)
members. The step-level file is sorted with NODUPKEY to
eliminate duplicate SYSIDs.  A SAS data set is built using
the variables listed below, which are required for the PROC
FORMAT to create your SAS format
 
o  FMTNAME - Name of format
o  START   - Low end of range
o  END     - High end of range
o  LABEL   - Value to be set
 
The PROC FORMAT, using the SAS control CNTLIN, inputs the SAS
data set created in the previous data step and writes the
format to the prefix.MICS.MUOLIB library. Another PROC FORMAT
reads in the format library to create a SAS data set to print
the format contents.
 
 //jobcard
 /*JOBPARM LINES=99,COPIES=1
 //PROCS JCLLIB ORDER=(sharedprefix.MICS.PROCLIB)
 //*
 //SASSTEP EXEC MICSSHRn,
 //  SYSPARM=
 //CHECKPT DD DISP=SHR,DSN=prefix.MICS.CHECKPT.DATA
 //DETAIL DD DISP=SHR,DSN=prefix.MICS.DETAIL
 //SYSIN DD *
 OPTIONS DATE LINESIZE=80;
 
 DATA FILE1(KEEP=SYSID SYSNAME);
 SET &BATX..BATxxx01 ;
 
 PROC SORT DATA=FILE1 NODUPKEY;
   BY SYSID;
 
 PROC PRINT;
 
 DATA SYS1(KEEP=SYSNAME SYSID START LABEL END FMTNAME);
     RETAIN FMTNAME '$format';
     LENGTH
       START $16
       END   $16
       LABEL $40;
 
   SET FILE1 END=FINISH;
       START=SYSNAME;
       END=SYSNAME;
       LABEL=SYSID;
       OUTPUT;
 
   IF FINISH THEN DO;
      START='OTHER';
      END='OTHER';
      LABEL='****';
      OUTPUT;
   END;
 
 LIBNAME FMTS 'prefix.MICS.MUOLIB' DISP=OLD;
 PROC FORMAT LIBRARY=FMTS.MICSFMTS  CNTLIN=SYS1;
 
 LIBNAME UNIT 'prefix.MICS.MUOLIB' DISP=SHR;
 PROC FORMAT CNTLOUT=MAPSYS
     LIBRARY=UNIT.MICSFMTS;
     SELECT $format ;
 
 PROC PRINT;
 RUN ;
 
In user exit, sharedprefix.MICS.SOURCE(#SMFEXIT) _USRSSRE,
the new format can be applied with a PUT statement.
 
SYSIDRE=PUT(RENSYSNM, $format.);
 
This PUT statement will format the system name from the
multisystem enclave work file, BATREX, to the logical SYSID
assigned in your complex-level or unit-level definitions.
The BATREN file is created from the BATREX file in the merge
phase of the daily process.
 
Important!  This mapping is done because the data element
SYSIDRE in the BATREX file will become SYSID in the BATREN.
SYSID is the primary key in the BATREN file sort key.