ACFESGP-E-SGP Conversion Utility

Conversion Utilities › ACFESGP-E-SGP Conversion Utility

ACFESGP-E-SGP Conversion Utility

ACFESGP facilitates migration from existing E‑SGP records and OS/390 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 utility is available for sites currently using E‑SGP entry records for source groups and OS/390 Note 4 users using E‑SGP records for resource groups.

This utility creates input statements for the CONVESGP EXEC 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

CONVESGP INPUT A: The input statements that ACFESGP creates.

Running ACFESGP

The syntax for this utility is:


ACFESGP      [ DELETE|NODELETE           ]
             [ RECTYPE(XSGP|XRGP)        ]
             [ CONVMASK(-|recordkeymask) ]

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 you do not specify CONVMASK, the default is DELETE.
When you specify CONVMASK, the default is NODELETE.

RECTYPE(XSGP|XRGP)

Specified with one of two values:

XSGP

Translates the E‑SGP records into X‑SGP records for source grouping. This is the default.

XRGP

Translates the E‑SGP records to X‑RGP records for resource grouping.

CONVMASK(‑|record‑key‑mask)

Specifies a masked record key pointing to the records to convert. You can use any E‑SGP record mask for the records you need to convert. This is dependent on the naming conventions in effect at your site. The default for this parameter converts all E‑SGP records.

Run this utility with the parameters set to accommodate your conversion requirements. For example:

ACFESGP DELETE RECTYPE(XSGP)

With this example, CA ACF2 for z/VM creates control statements to convert all E‑SGP records to X‑SGP records. CA ACF2 for z/VM also creates control statements to delete the converted E‑SGP records from the database.

Note: 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. The utility performs these functions:

The new XREF record for the individual source names is inserted. This record name is Xn, 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 Xn 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 Xn 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, CA ACF2 for z/VM compares the name 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
GROUP 1: 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)

Converted to E‑SGP Records

X‑SGP Records

GROUP 1:

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 not active.

For more information about return codes, see the output messages the ACFESGP utility returns.

Example

Run the ACFESGP utility. For example, enter:
```
ACFESGP (parms as needed
```
To run ACFESGP, the logonid of the user must have CA ACF2 for z/VM read access to the E‑SGP records that are converted.
CA strongly recommends that you convert E‑SGP records at one time with all records and the DELETE option chosen. If you cannot 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.
Edit the control statements in the CONVESGP INPUT file ACFESGP created. Change the Xn record names to the naming convention that your site established. Be sure to edit the Xn names in both the insert control statements. For example, you can change:
```
INSERT X0000001 SOURCE -
       INCLUDE(LV1,LV2)
INSERT GROUP1 GROUP -
       INCLUDE(GRP2,GRP3,X0000001)
```
To:
```
INSERT GRP4 SOURCE -
       INCLUDE(LV1,LV2)
INSERT GROUP1 GROUP -
       INCLUDE(GRP2,GRP3,GRP4)
```
An XREF record uses more space for the same number of items than an ESGP record does. You might need to split very large ESGP records into two XREF records and create an XREF GROUP record to associate the new records.

For XRGP RESOURCE records, the keyword TYPE(...) is generated for each record. When editing the output, change the (...) to the appropriate three character resource type.
Run the CONVESGP EXEC. This exec submits the control statements in the CONVESGP INPUT file to the ACF command. These control statements insert new X‑SGP or X‑RGP records and delete the old E‑SGP records, if you specified the DELETE parameter.
CONVESGP spools console to your ID and starts console spooling. When done, CONVESGP stops console spooling.