Upgrading File-AID/Data Solutions custom date pattern and field level exits

Task 5.1.1 Determine if you are using a Supplied Date Pattern Exit

Since Data Solutions is distributed with more than 50 date exits, it handles the vast majority of the date formats you encounter in your data. The following table describes the characteristics of the sample formatted date pattern exits supplied with File-AID.

Supplied Date Pattern Exits

Task 5.1.2 Customizing Date Pattern Exits

If you want to add your own date pattern exits for processing by Data Solutions, you need to do the following:

1. Use one of the File-AID-provided COBOL date exits, AGERnnnn-named members in the sample library (hlq.SXVJSAMP), as a model. Look for an exit that is similar to your date pattern. Save it under a new date exit name, use AGER0700 – AGER0999 if the exit is non-LE enabled or AGER1000 – AGER9999 if the exit is LE enabled. Make any modifications or adjustments required for your date pattern. Use UDAEXITL in the sample library (hlq.SXVJSAMP) to compile and link your new date pattern exit.

2. Identify your environment library names (See Step 12. Specify External Files in the BMC Installer Mainframe Products SMP/E Installation).

3. Update DATELIST in hlq.SXVJSAMP to add your new date pattern exit.
4. Use sample JCL UDADLIST in the sample library (hlq.SXVJSAMP) to assemble and link to LOAD module DATELIST in your Configuration LOAD library (hlq.CXVJLOAD).

Each entry in the Date Pattern Exit Table consists of the following six fields:

Data type

Specify B (Binary), C (Character), G (Graphic, Double Byte Character Set), N (Numeric), P (Packed), V (Variable length Character), or W (Variable length Graphic, Variable length Double Byte Character Set). The data type is determined by the record layout specified for the Formatted aging criteria. It has a length of one byte. If your exit handles more than one data type, add a date entry for each data type to the Date Pattern Exit Table (DATELIST).

Date pattern name

Specify a unique name alphanumeric 1 to 15 characters. The date pattern name is the name that you specify on the Formatted Aging Criteria screen or select from the Available Date Patterns screen.

Date length

Specify the number of bytes (not digits) that Data Solutions will pass to and return from the date pattern exit. For example, packed 7 digits is 4 bytes.

Load module name

Specify the load module name of your new exit (AGER0700 – AGER0999 if the exit is non-LE enabled or AGER1000 – AGER9999 if the exit is LE enabled). It must begin with “AGER” and end with a four-digit number from 0700 to 9999. Numbers from 0000 to 0699 are reserved for date pattern exits written by BMC.

Description

Specify up to 30 characters describing your new date pattern exit. This description is displayed on the Available Date Patterns screen.

Filler

Specify a 3 byte filler.

Date Exit Compile/Link JCL

Add the appropriate information (in Date Exit Compile/Link JCL) for your COBOL date exit to the Date Pattern Exit Table in Sample PDS member DATELIST. Use UDADLIST to reassemble and link edit the table.

The following figure shows the date pattern exit flow for File-AID/Data Solutions and COBOL.

File-AID/Data Solutions and COBOL Date Pattern Exit Flow

Task 5.2 Upgrading BMC AMI DevX File-AID/Data Solutions Custom Field Level Exits

Task 5.2.1 Determine If You are Using a Supplied Field-Level Exit

File-AID uses field-level exits shown in the following table to define and process both Data Solutions-defined and user-defined business function data conversions. Data Solutions takes the specified data field, passes it to the field-level exit for conversion, and returns the new value to the data field. File-AID is distributed with the field-level exits.

Data Solutions Field-Level Exits

Task 5.2.2 Add Your Own Field-level Exits

If you want to add your own field-level exits for processing by File-AID, you need to do the following:

1. Use one of the File-AID-provided COBOL field-level exits, EXITnnnn-named members in the sample library (hlq.SXVJSAMP), as a model. Save it under a new exit name EXIT0700 – EXIT0999 if the exit is non-LE enabled or EXIT1000 – EXIT9999 if the exit is LE enabled. Make your modifications. Use UDAEXITL to compile and link your new field exit.

2. Identify your environment library names (See Step 12. Specify External Files in the BMC Installer Mainframe Products SMP/E Installation).

3. Update EXITLIST in hlq.SXVJSAMP to add your new field exit.

4. Use sample JCL UDAELIST in the sample library (hlq.SXVJSAMP) to assemble and link to LOAD module EXITLIST in your Configuration LOAD library (hlq.CXVJLOAD).

   Each entry in the Field-Level Exit Table consists of the following fields:

   Data type

   Specify B (Binary), C (Character), G (Graphic, Double Byte Character Set), N (Numeric), P (Packed), V (Variable length Character), or W (Variable length Graphic, Variable length Double Byte Character Set). The data type is determined by the record layout specified for the field exit criteria. It has a length of one byte. If your exit handles more than one data type, add an entry for each data type supported to the Field-Level Exit Table (EXITLIST).

   Field-level exit name

   Specify a unique name alphanumeric 1 to 15 characters. The exit name is the name that you specify on the Formatted Field Exit Criteria screen or select from the Available Field Exits screen.

   Warning

   Important

   The combination of name and data type must be unique. If multiple entries have the same name and data type, only the load module of the first entry will be executed.

   Field length

   Specify the maximum number of bytes (not digits) that Data Solutions will pass to and return from the field exit. For example, packed 7 digits is 4 bytes. (An exit can process fields of various lengths.)

   Load module name

   Specify the load module name of your new exit (EXIT0700 – EXIT0999 if the exit is non-LE enabled or EXIT1000 – EXIT9999 if the exit is LE enabled). It must begin with “EXIT” and end with a four-digit number from 0700 to 9999. Numbers from 0000 to 0699 are reserved for field-level exits written by BMC.

   Description

   Specify up to 30 characters describing your new field-level exit. This description is displayed on the Available Field Exits screen.

   Filler

   Specify a 3 byte filler.

   Warning

   Important

   • For encryption/decryption exit the first byte of “Filler” is used for an exit type descriptor of E. This allows File-AID to differentiate when displaying Available Field Exits for Option 6 (Field Exits) and Available Encryption/Decryption Exits for Option 7 (Data Encryption).
   • To avoid assembling and linking EXITLIST every time anyone at your site wants to add a new field exit is to add a group of new entries at one time and assign one or more to each programmer. Once the assigned field-level exit entry (hook) is linked into Data Solutions, each programmer can modify and test their field exits without requiring a systems programmer to modify EXITLIST.
   • To compile and link edit your new COBOL field-level exit, use the JCL that is appropriate for your COBOL version (see Field-Level Exit Complile/Link JCL).

   Field-Level Exit Complile/Link JCL

   COBOL Version	Use JCL:
   LE 370 / COBOL for MVS	UDAEXITL

5. Add the appropriate information (listed above) for your COBOL field-level exit to the Field-Level Exit Table in the sample library (hlq.SXVJSAMP) member EXITLIST.
6. Use UDAELIST to reassemble and link edit the table.