Default language.

Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Load for Db2 13.1.

NGT1DBUT to copy BMC AMI Utilities VSAM work files

You can use the NGT1DBUT program to copy the 

BMC AMI Utilities

 VSAM work files ( .OUT and .INFO) to sequential data sets. You can then view or send these sequential data sets to BMC Customer Support for further analysis. NGT1DBUT supports two SYSIN statements; one to dump the work files, and one to extract them. Sample jobs can be found in the hlq.BMCCNTL PDS, members NGT1DB2T and NGT1DBUT.

DBUT DUMP utility command syntax

DBUT_DUMP.png

JOBNAME

(required) A 1- to 8-byte job name.

JESID

(required) An 8-byte JES ID.

STEPNAME

(optional) A 1- to 8-character name associated with a step in a multi-step job.

OUTDD

(optional) A 1- to 8-byte DD name in the JCL. The default ddname is OUTFILE.

DBUT EXTRACT utility command syntax

DBUT_EXTRACT.png

FILE

(required) Which BMC AMI Utilities work file to extract, INFO or JRNL. JRNL, known as the Journal, refers to the .OUT work file.

INDD

(optional) The BMC AMI Utilities work file data set name. The default ddname is INFILE.

OUTDD

(optional) A 1- to 8-byte DD name in the JCL. The default ddname is OUTFILE.

Important

Note the following considerations when you configure the NT1DBUT command:

  • The optional STEPNAME keyword allows a single step of a multi-step job to be DUMPed, independently of other steps within the job.
  • The STEPNAME keyword can be omitted or present for single step jobs, but if omitted for multistep jobs, the entire job including all associated steps are dumped.
  • If multiple steps within the same job are to be dumped, then it is required that these be dumped to separate output data sets, because of the excessive amounts of data, and in order to facilitate ease of diagnosis by development.
  • In data sharing installations in which two or more Db2 subsystems are shared under a common group name, the group name should be specified rather than the name of an individual Db2 subsystem in the group.
Example of an NGT1DBUT JCL job
//NGT1DBUT JOB . . .
//JOBLIB DD DISP=SHR,DSN=<your.ngt.loadlib>
//STEP01 EXEC PGM=NGT1DBUT,PARM='DSNA,,NORESTART'
//SYSPRINT DD SYSOUT=*
//OUTFILE DD DISP=(,CATLG),DSN=<your.journal.datasetname>,
// UNIT=SYSALLDA,SPACE=(CYL,(5,50),RLSE)
//SYSIN DD *
DBUT DUMP JOBNAME(<jobname>) JESID(JOB31569)
//
//NGT1DBUT JOB . . .
//JOBLIB DD DISP=SHR,DSN=your.ngt.loadlib
//NGT1DBUT EXEC PGM=NGT1DBUT,PARM='DSNA,,NORESTART'
//CDBPRINT DD SYSOUT=*
//INFILE DD DISP=SHR,DSN=workprefix.MMBNLNJG.OGAEFLAA.OUT001
//OUTFILE DD UNIT=SYSDA,DISP=(NEW,CATLG,DELETE),
// DSN=<your.journal.datasetname>,
// SPACE=(TRK,(1,5),RLSE)
//SYSIN DD *
DBUT EXTRACT FILE(JRNL)
//

Related topic

Getting-started

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*