Data Build Manual

User Exits
Customizing Data Build
6–8 099331 Tandem Computers Incorporated
4. Create and compile the SIGNDNUM program.
5. If the compiled object module does not exist in the conversion subvolume, add a ?
SEARCH statement at any user exit in USERLIB.
6. Complete the CREATE (F4) step and check the spooler output.
7. Perform the RUN (F5) step as usual.
If SIGNDNUM is coded in COBOL85, an alternate to using SIGNDNUM as an
external called module, is to change the CALL "SIGNDNUM" to PERFORM
SIGNDNUM and include a SIGNDNUM paragraph with the conversion code.
User Exits User exits are supported at strategic points in the conversion program. If it does not
already exist, a user library file named USERLIB is created on the conversion project
subvolume during the GENERATE (F3) step. USERLIB contains a clearly named
section for each user exit; user code can be added to any section using an editor. Each
section is copied into the generated COBOL85 conversion program via COPY
statements during the CREATE (F4) step.
Customized routines can be executed before conversion processing begins, after
processing concludes, before and after each record is converted and before and after
each field within a record is processed. PERFORMed user routines can be included at
the end of the program. User working storage elements and special names can also be
defined.
If USERLIB already exists (most likely from a previous F3 step on this project
subvolume), the following messages are issued:
GENPROC: User Library Exists - $Vol.subvol.USERLIB
GENPROC: If You Wish To Purge, Enter Y/N...
Y will purge the current file and recreate the skeleton file.
Many sections in USERLIB are named from the field names in the Source Record
Descriptions File. If any field names changed you must enter Y, otherwise you can
enter N if you wish. If USERLIB has been previously modified, you would generally
respond N to preserve the changes, or respond Y if any needed changes have been
previously saved.