ACFESGP - E-SGP Conversion Utility

Describes the ACFESGP E-SGP conversion utility.
acf2src
CA ACF2 for z/OS
provides the batch conversion utility, ACFESGP, to facilitate migration from existing E-SGP records and Note 4 definitions to cross-reference (XREF) records. These XREF records, X-SGP and X-RGP, are used for source and resource grouping, respectively. This batch utility is available for sites currently using E-SGP entry records for source groups and Note 4 users using E-SGP records for resource groups.
This utility creates input statements for the ACFBATCH utility that you can edit as appropriate. Before running the conversion utility, set up a naming convention that meets your site's grouping requirements. It is important that this naming convention is compatible with the masking capabilities available with the source and resource grouping feature.
Files
  • SYSUT1
    Points at the data set, or SYSOUT, where the control statements are built. This DD statement should point to a data set that is used as input to the ACFBATCH utility.
Parameters
  • [DELETE|NODELETE]
    DELETE creates a control statement to delete the old format E-SGP record after the control statements for inserting the new X-SGP record are created. The default depends on the CONVMASK parameter. For example:
    • When CONVMASK is not specified, the default is DELETE.
    • When CONVMASK is specified, the default is NODELETE.
  • [RECTYPE(XSGP|XRGP)]
    Specifies with one of two values:
    • XSGP-the E-SGP records are translated into X-SGP records for source grouping. This is the default.
    • XRGP-the E-SGP records are translated to X-RGP records for resource grouping.
[CONVMASK(-|record-key-mask)]
Specifies a masked record key pointing to the records to convert. You might use any E-SGP record mask for the records you must convert. This is dependent on the naming conventions in effect at your site. The default for this parameter converts all E-SGP records.
Run the conversion utility with the parameters set to accommodate your conversion requirements. For example:
//CONVERT EXEC PGM=ACFESGP,PARM='DELETE,RECTYPE(XRGP)'
With this example, control statements are created to convert all E-SGP records to X-RGP records. Control statements are also created to delete the converted E-SGP records from the database.
: When group records in the E-SGP format contain both individual source names and E-SGP group name entries, this utility creates control statements to separate the individual source names into a newly created record. For example, the E-SGP record of GROUP1 contains individual sources (LV1 and LV2) and E-SGP group name entries (GRP1 and GRP2). LV1 and LV2 are placed in a new XREF (X-SGP) record. This utility then converts the E-SGP record to another XREF record containing the newly created record for the individual sources and the E-SGP group name entries.
Utility Functions
The utility performs these functions:
  • The new XREF record for the individual source names is inserted. The record name is X
    n
    , where
    n
    is a binary number starting at 0000001 and one is added for each new record created. The first new record is X0000001; the second is X0000002; and so on.
  • When the X
    n
    type XREF record is inserted, all individual source names from the E-SGP record are placed in that record. The SOURCE keyword indicates that all entries in this record are individual source names. For example:
    INSERT X0000001 SOURCE INCLUDE(LV1,LV2)
  • Another XREF record is created from the old E-SGP group name entries. This new record's name is the same name as the old E-SGP record that is converted. The new X
    n
    type XREF record name is added to this XREF record to form the same group configuration as before the conversion. The GROUP keyword indicates that all entries in this record are source group records. For example:
    INSERT GROUP1 GROUP INCLUDE(GRP1,GRP2,X0000001)
To determine if an E-SGP record name is an individual source record or group record name entry, the name is compared to all the group record names in the E-SGP section of the Infostorage database.
  • If a match occurs, the E-SGP record name is considered a group record name.
  • If a match does not occur, the E-SGP record name is considered an individual source record name. For example:
Converted to E-SGP Records
X-SGP Records
GROUP1:
LV1
LV2
GRP1
GRP2
GROUP1 GROUP
INCLUDE(GRP1,GRP2,X0000001)
X0000001 SOURCE
INCLUDE(LV1,LV2)
GRP1:
LV6
LV7
GRP1 SOURCE
INCLUDE(LV6,LV7)
GRP2:
LV3
LV4
GRP2 SOURCE
INCLUDE(LV3,LV4)
Return Codes
ACFESGP can return the following return codes in Register 15:
  • 0
    Conversion performed without error.
  • 4
    Error occurred during conversion. Refer to messages.
  • 8
    Invalid parameter specified or CA ACF2 is not active.
  • 12
    SYSUT1 DD statement invalid of missing.
For more information on return codes, see the job output for messages returned by the ACFESGP utility.
Procedures
  1. Write JCL that runs the ACFESGP batch utility. The ACFESGP batch conversion utility is located in the CAI.ACF2.ACFMOD data set. The following is an example of the JCL needed to run the batch conversion utility:
    //SGPCONV JOB SGP,'CONVERT E(SGP) RECORDS',MSGCLASS=X //CONVERT EXEC PGM=ACFESGP,PARM='parms as needed' //STEPLIB DD DISP=SHR,DSN=CAI.ACF2.ACFMOD //SYSUT1 DD DSN=data set in which control statements are to be placed or SYSOUT=*
    To submit the conversion utility, the logonid of the user must have read access to the E-SGP records that are converted.
  2. Run ACFESGP utility. We strongly recommend that conversion of E-SGP records is done at one time with all records and the DELETE option chosen. If you are unable to convert all E-SGP records at one time, use the NODELETE option to ensure that the conversion utility can correctly determine which E-SGP records are source entries and which are group name entries.
  3. Edit the control statements. After step two is completed, edit the control statements created by the utility. Change the X
    n
    record names to the naming convention that was established by your site. Be sure to edit the X
    n
    names in both the insert control statements. For example:
    INSERT X0000001 SOURCE INCLUDE(LV1,LV2) INSERT GROUP1 GROUP INCLUDE(GRP2,GRP3,X0000001)
    Can be changed to:
    INSERT GRP4 SOURCE INCLUDE(LV1,LV2) INSERT GROUP1 GROUP INCLUDE(GRP2,GRP3,GRP4)
    For XGRP RESOURCE records, the keyword TYPE(...) are generated for each record. When editing the output, you should change the (...) to the appropriate three character resource type.
  4. Run the ACFBATCH utility with the edited control statements. After completing step three, run the ACFBATCH utility with the control statements as input. These control statements insert new X-SGP or X-RGP records and delete the old E-SGP records, if the DELETE parameter is specified. For more information about running the ACFBATCH utility, see The ACF Command in Batch.