Customizing the NGLARCH started task
NGL provides a process to archive the data written to the log files. A sample PROC, NGLARCH, is delivered in the SAMP data set and might need to be customized and copied to your SYS1.PROCLIB (or equivalent) started task library (depending on the products installed).
The NGLARCH started task is spawned by the DBC started task when an archive is requested. DBC spawns NGLARCH when one of the following conditions occur:
- A log file is full.
- SWITCH command is issued.
The definition for the NGL agent identifies the name of the NGLARCH started task.
To update or change the name in the agent definition
- Edit the NGLINIT step from the $465INIT installation job.
Locate the <PROCNAME> element:
<procname>NGLARCH</procname>Change the name to match the member name in your system PROCLIB and rerun that step.
Execute the NGL,REFRESH,piid command, where piid indicates the product instance identifier. For more information about NGL commands, see NGL-commands.
The following figure shows an example of this started task.
NGLARCH started task
//NGLARCH EXEC PGM=NGL9ARCH,
// ACCT=????,REGION=0M
//STEPLIB DD DISP=SHR,DSN=?BMC_HLQ?.NGLLINK
// DD DISP=SHR,DSN=?BMC_HLQ?.DBCLINK
// DD DISP=SHR,DSN=?BMC_HLQ?.DOMLINK
//SYSPRINT DD SYSOUT=*
//REPORT DD SYSOUT=*
//NGL$DUMP DD DUMMY
The following table describes the DD statements included in the NGL started task.
DD statements for NGLARCH started task
DD statement | Explanation |
|---|---|
STEPLIB | The location for NGL, DBC, and DOM load libraries. Depending on the options chosen during the install, the NGL, DBC, and DOM load libraries might be three separate libraries or they might be all in the same library. |
SYSPRINT | Identifies the data set to write potential non-DBC product application messages. |
REPORT | Identifies the data set that contains the output of the NGLARCH process. |
NGL$DUMP | A dummy statement to be used if a dump has been requested by BMC Support. |