Creating external vendors
RUV allows an interface to products created by other vendors. Functional events in RUV such as ADD, UPDATE, DELETE, journaling, and registration activities can be provided to an external vendor exit program as data records.
When z/OS initializes, all standard subsystems and address spaces are started. BCSS locates all external vendor records within a rule set and reads the repository to determine whether certain events are to be enabled.
From those external vendor records, BCSS builds an external vendor list with an entry for each of the specified vendors. Only active vendors are used. The external vendor interface is then ready to process external vendor programs.
This topic contains the following information:
Using the ADD EXTERNAL_VENDOR command
Use the ADD EXTERNAL_VENDOR command to create an external vendor program record. This record will be used by the ACTIVATE RULE_SET command if any external vendors are identified in the rule set being activated.
To code an ADD EXTERNAL_VENDOR statement, use the following syntax:
{ COMMENT(comment_fields) }
{ STATUS(ACTIVE | INACTIVE) }
{ BACKUP_REGISTRATION(NO | program8
{, “initialization parameters” }) }
{ JOURNAL_REGISTRATION(NO | program8
{, “initialization parameters” }) }
;
Using the UPDATE EXTERNAL_VENDOR command
Use the UPDATE EXTERNAL_VENDOR command to update an external vendor program record. This command uses the same keywords and values that the ADD EXTERNAL_VENDOR command uses.
{ COMMENT(comment_fields) }
{STATUS(ACTIVE | INACTIVE) }
{ BACKUP_REGISTRATION(NO | program8
{, "initialization parameters" } ) }
{ JOURNAL_REGISTRATION(NO | program8) }
{, "initialization parameters" } ) }
;
Using the STATUS keyword
The STATUS keyword activates or deactivates use of the EXTERNAL_VENDOR. The following values are valid for the STATUS keyword. The default value is ACTIVE.
Value | Use |
|---|---|
ACTIVE | Use this value to activate use of the EXTERNAL_VENDOR. |
INACTIVE | Use this value to deactivate use of the EXTERNAL_VENDOR. |
Using the BACKUP_REGISTRATION keyword
The BACKUP_REGISTRATION keyword specifies external vendor exit backup programs and parameters. Two or more EXTERNAL_VENDOR commands can have backup registration keywords that refer to the same program.
The following values are valid for the BACKUP_REGISTRATION keyword. The default value is NO.
Value | Use |
|---|---|
NO | Use of this value prevents EXTERNAL_VENDOR from notifying an external vendor exit that RUV backup data is available. |
program8 | Use of this value allows EXTERNAL_VENDOR to notify an external vendor exit that backup data is available. |
Initialization Parameters | Actions of the external vendor's program customize the initialization parameters. The external vendor is responsible for providing you with this information. |
Using the JOURNAL_REGISTRATION keyword
The JOURNAL_REGISTRATION keyword specifies user exit journal programs and parameters. Two or more EXTERNAL_VENDOR commands can have journal registration keywords that refer to the same program.
The following values are valid for the JOURNAL_REGISTRATION keyword. The default value is NO.
Value | Use |
|---|---|
NO | Use of this value prevents EXTERNAL_VENDOR from notifying an external vendor exit that RUV journal data is available. |
program8 | Use of this value allows EXTERNAL_VENDOR to notify an external vendor exit that journal data is available. |
Initialization Parameters | Initialization parameters are used to customize the actions of the external vendor's program. The external vendor is responsible for providing you with this information. |
Using the RUV-provided external vendor
RUV provides an exit program called RUVSTAT that can be used for the program8 value. The EXTERNAL_VENDOR program RUVSTAT will provide batch job statistics at step termination. Under optional initialization parameter control, you specify that RUVSTAT print this journal information to the CONSOLE or JESYSMSG.
The following example specifies the following items:
- The default external vendor (RUVSTAT) is active.
- Statistics will be reset to 0 and gathered.
- Registration of journal statistics is printed to JESYSMSG.
STATUS(ACTIVE)
JOURNAL_REGISTRATION(RUVSTAT JESYSMSG)
;
The following figure shows a sample RUVSTAT printout:
* JOBNAME : DOPRNT1 STEPNAME: PRTARCH *
* SUBSYSTEM : RUV1 *
* DSN: RUVRUV.DV70IVP.RUVEBASE *
* 1 Opens 1 Closes *
* 4 Adds 2 Updates *
* 0 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RUVESMS0 *
* 1 Opens 1 Closes *
* 4 Adds 2 Updates *
* 0 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RUVE0010 *
* 1 Opens 1 Closes *
* 4 Adds 2 Updates *
* 0 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RUVKBASE *
* 1 Opens 1 Closes *
* 1 Adds 0 Updates *
* 6 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RUVKDPV0 *
* 1 Opens 1 Closes *
* 4 Adds 2 Updates *
* 6 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RUVKPTH1 *
* 1 Opens 1 Closes *
* 1 Adds 1 Updates *
* 0 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RUVKRKP9 *
* 1 Opens 1 Closes *
* 4 Adds 2 Updates *
* 6 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RUVKSMS0 *
* 1 Opens 1 Closes *
* 4 Adds 2 Updates *
* 6 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RUVK0010 *
* 1 Opens 1 Closes *
* 4 Adds 2 Updates *
* 6 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RURUVMS0 *
* 1 Opens 1 Closes *
* 4 Adds 2 Updates *
* 6 Deletes 0 Discards *
* DSN: RUVRUV.DV70IVP.RUVR0010 *
* 1 Opens 1 Closes *
* 4 Adds 2 Updates *
* 6 Deletes 0 Discards *
* *
********************************************************************************
Activating the EXTERNAL_VENDOR
The ACTIVATE RULE_SET command activates an ADD EXTERNAL_VENDOR command or an UPDATE EXTERNAL_VENDOR command.
Using the DELETE EXTERNAL_VENDOR command
Use the DELETE EXTERNAL_VENDOR command to remove an interface with an external vendor program. See Deleting-rule-set-elements for coding instructions.
Related topic