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.
- An ARCHIVE LOGSET command is issued for the NGL piid (for more information, see NGL-commands).
Agents currently using the NGLARCH started task are:
- DB2 Data Collector (DOM)
- Mainview Logger (MVL)
To update or change the name in the agent definitionNGL PIIDs receive default values for parameters from the NGLOPTS member referenced on the DBCENV DD in the DBC started task PROC (where piid is the product instance identifier). To change the default name of the NGLARCH started task for all NGL PIIDs, edit the NGLOPTS member and change the value for the ARCHPROC keyword. To override the default name for any specific PIID, edit the NGLpiid member in the DBCENV data set and change the value for the ARCHPROC keyword. If there is no ARCHPRO statement, insert a new one.
- Edit the NGLpiid member in the data set referenced on the DBCENV DD in the DBC started task PROC (where piid is the product instance identifier).
Locate the ARCHPROC= line and change the value on the right-hand side of the equal sign to the new value that matches the member name in your system. If there is no ARCHPROC= line, insert a new one. - Refresh the NGL PIID.
- For the DOM agent, issue the command /dbcssid DBC,EXEC,DOM (where dbcssid is the DBC subsystem identifier). This command refreshes the DOM agent as well as its PIID.
- For the MVL agent, issue the command /dbcssid DBC,EXEC,MVL (where dbcssid is the DBC subsystem identifier). This command refreshes the MVL agent as well as its PIID.
- For all other client NGL products using a PIID, issue the command /dbcssid DBC,EXEC,NGL,piid (where dbcssid is the DBC subsystem identifier and piid is the product instance identifier).
The following figure shows an example of this 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=*
//TERSE DD DUMMY
//NGL$DUMP DD DUMMY
The following table describes the DD statements included in the NGL started task.
DD statement | Explanation |
|---|---|
STEPLIB | The location for NGL, DBC, DOM, and MVL load libraries. Depending on the options chosen during the install, the NGL, DBC, DOM, and MVL load libraries might be 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. |
TERSE | A dummy statement to be used if the purge data set report is to be abbreviated to only those data sets being deleted. |
NGL$DUMP | A dummy statement to be used if a dump has been requested by BMC Support. |
Related topic