Home About us Search Contact us Sitemap Sign-in
Support
 
Software
News
Purchase
Download
Support
Installation
New page


Can't find the answer ?
Send us an email.

Dbugpgm

Starting a DBUG session for a target program running in a batch partition

On a CICS screen FIRST enter:
DBUG PROG=xxxxxxxx

and press ENTER, or you may, optionally, add further parameters for DBUG viz:
DBUG PROG=xxxxxxxx,CLASS=z,PART=yy

PROG is not an abbreviation for PROGRAM
PROG specifies the target program name (phase name)
CLASS=z specifies a POWER LST class for the Source Listing (Default=Z)
PART specifies the target partition (Default is any)

Now run the Batch job containing the target program

Starting a DBUG session for a target program or transaction running in CICS

On a CICS screen FIRST enter:
DBUG PROG=xxxxxxxx
or
DBUG TRAN=xxxx

and press ENTER, or you may, optionally, add further parameters for DBUG viz:
DBUG PROG=xxxxxxxx,CLASS=z,TERM=xxxx
or
DBUG TRAN=xxxx,CLASS=z,TERM=xxxx

PROG is not an abbreviation for PROGRAM
PROG specifies the target pgrmid
CLASS=z specifies a POWER LST class for the Source Listing (Default=Z)
TRAN specifies the target transid
Now start the target CICS program or transaction



See our Download page to obtain a copy of the above entire on-line help formatted as a handy Quick-Ref PDF file - it contains full information on how to drive Dbugpgm

Despool

Use the following JCL as a sample
* $$ JOB JNM=DESPOOL,CLASS=Z,DISP=K
* $$ LST CLASS=A,DISP=H
// JOB DESPOOL
// SETPARM LIB='PRD4'
// SETPARM SLIB='LOCAL'
// LIBDEF PHASE,SEARCH=&lib..&sublib,TEMP
// LIBDEF SOURCE,SEARCH=&lib..&sublib,TEMP
/*
* Note: Use 'MSG XX' to communicate with DESPOOL
* Note: Use 'MSG BG,DATA=XXXXXXXX' if on an applicable VSE release
/*
/* Note: The next ASSGN/DLBL/EXTENT is only required if you want
/* output spooled to a sequential (or VSAM Managed Sam) disk
/* file. It is ignored if you are spooling output to TAPE.
/* Ensure you update the volser, file-name, and extents.
/*
// ASSGN SYS020,DISK,VOL=SYSWK3,SHR
// DLBL DTFDASD,'##.IJSYSIN.WORK',0,SD,CISIZE=32768
// EXTENT SYS020,SYSWK3,1,0,418048,10240
/*
/* Note: You may place any parameters provided on the // EXEC PARM in the
/* DESPOOL.CONFIG member. Parameters specified on the // EXEC PARM
/* take precedence over those in DESPOOL.CONFIG.
/*
// EXEC LIBR,SIZE=256K,PARM='ACCESS S=&LIB..&SLIB'
CATALOG DESPOOL.CONFIG REPLACE=YES
CLASS=A,CODE=........................
*
* Note: All lines starting with an asterisk (*) are comments
*
START,COL=4,TEXT='DIVISION 4',NAME=DIV4STOK,CLASS=A,COPY=2,FNO=ABCD
END,COL=12,TEXT='TOTAL'
START,COL=4,TEXT='DIVISION 12',NAME=DIVCSTOK,CLASS=A,COPY=2,FNO=ABCD
END,COL=12,TEXT='TOTAL'
/+
/*
// EXEC DESPOOL,SIZE=256K,PARM='CLASS=Z,CCW=0101,COM=XPCC,PCHEK=NO,+
                RECYCLE=0,SAT=YES,TAPE=580,TRACE=NO,USER=PSF,WAIT=2,',+
                PARM='COUNT=NO,MSG=3,PANEL=YES'
/*
// IF $RC=0 THEN
// GOTO END
// PAUSE - DESPOOL RETURNCODE NOT = 0
/. END
/*
/&
* $$ EOJ

Minimon

On a CICS screen enter:
MINI

Press ENTER when prompted

Navigation to different screen displays in Minimon.

All Minimon commands are of the format:

MINI cmd pt operands

were MINI is the CICS transid
       cmd is the 4-character command name
       pt is the target partition if required
       operands are any operands if required

Note that Minimon transactions may also be entered via the system console (Termid = CNSL), however output will be limited to specific messages written to SYSLOG.

The initial menu has a command name of MENU.

Navigation using the cursor select facility.

All screens with a + symbol at the top right of the screen are cursor select enabled. This means you may place the cursor, using the cursor movement keys, on any part of a line denoting that you wish to navigate to that screen. Tap the enter key to display the selected screen. If there is a target partition or operands required on the MENU screen you will be prompted to enter them at the top left of the screen before being taken to your selected choice. Cursor select is available for the following screens:
From To.. Data passed...
AIDS AIDS Selected AID address
ATFD TPPS Task number
CTBL SHOW Selected table entry virtual address
DBDS DBDS Database name
DSPT SHOW Dataspace virtual address
GETU SHOW Selected virtual address
GETV SHOW Selected page virtual address
HIST SIOD Device CCUU
ICES ICES Selected ICE address
LCLN SHOW Phase / Control Block address
LIBD LIBR Library and Sublibrary names
LIBR LIBR Library, Sublibrary or Member Name, Type
MENU .... Selected command and default operands
PAM1 SHOW Selected address within the DSA
SHOW SHOW Control Block address
TASK ATFD CICS Task number
TCPI TCPI TCP defined area name
TDAS TASK CICS Partition SYSLOG ID and 'EXEC'
TRAN ATFD CICS Task number
TSQS TSRD Temporary Storage queue name

After navigating from TRAN or TASK you may navigate to TPPS simply by entering MINI TPPS at the top left of the screen. The taskno will be passed to TPPS internally.

To display the CICS transaction averages for a particular CICS partition, since monitoring was started in that partition, enter:

MINI TRAN pt TRAN=....

where pt is the target partition SYSLOG id and the '....' is entered as shown. To display the CICS transaction totals simply enter:

MINI ATFD.

Transactions displayed may be limited by specifying:

MINI TRAN pt ABCD=abcd - to select by abcode
MINI TRAN pt TERM=term - to select by termid
MINI TRAN pt TRAN=tran - to select by transid
MINI TRAN pt PROG=prog - to select by pgrmid

For GETV and PAM1 placing the cursor on a displayed page in the map and pressing Enter will display target storage for that page.

On-line help for displayed screen field contents.

Position the cursor anywhere on a white heading word, on the third line of a screen and tap the Enter key. A pop-up will appear at the start of the word presenting details of the field's contents. Tapping Enter again, or navigating to another screen, will remove the pop-up. Note that this does not work for those screens using extended highlighting in their headings.

Data captured by Minimon for batch reporting.

Data is captured by Minimon while a batch program or a CICS transaction is running. When the task ends a record is written, in compressed format, to a table in the SVA. This provides a buffer in high transaction-rate systems and allows for online viewing of the last approximately 800 transactions. From this buffer transaction records are written to the MINIPRI and MINISEC file on sequential disk. These files are automatically opened alternately by Minimon, after startup, when the first CICS job starts CICS initialization and are closed automatically when Minimon detects there are no active CICS partitions still running.

The commands:

MINI DATA SWITCH will switch the active data collection file between PRImary and SECondary.

MINI DATA CLOSE will close the file until a:

MINI DATA OPEN command is issued irrespective of CICS jobs running.

Once the currently active data collection file, MINIPRI or MINISEC, has been closed it may be reported against using the sample JCL provided in VSE library member MINIREP.Z

MINIREP requires that the data collection file it processes is closed.

The currently active data collection file may be closed, manually, by issuing the

MINI DATA CLOSE command. It is also closed, automatically, when the current extent is full and an autoswitch to the alternate collection file occurs, or when the last active CICS partition terminates.

The message:
MINI130 NO VALID DATA RECORDS WERE READ; MINIREP REPORTS TERMINATED
is indicative of attempting to run MINIREP against a currently open data collection file.

Opening the current active MINIPRI or MINISEC file will result in records being written to the file starting from the beginning of the file again, overwriting previous records. Therefore the file should be copied to an alternative extent or archived, using any standard VSE utility, prior to reopening the file, unless the records therein are not required for future reporting. Also the file should be allocated sufficiently large in size to accommodate a reasonable amount of data. Each Batch job step and CICS transaction causes a 224-byte record to be written to this file.

PFKey settings for fast navigation.

PFKeys are setup as follows:
PF1 = Help which displays the Menu screen
PF2 = Help which displays the Menu screen
PF3 = Navigate up one level in multilevel displays
PF4 = Display Minimon Product Options popup
PF5 = Display Instruction Trace Control popup
PF6 = Display Memory Zap popup

The Memory Zap popup initially displays an initial popup so that a target partition syslog id and address may be entered. Pressing the Enter key will cause Minimon to fetch and display data at the nominated address in the Memory Zap popup. To change the storage contents at the nominated address overtype the displayed data (in hex) and press the Enter key. The storage will be altered, and the Memory Zap popup will no longer appear on the screen.

PF7 = Prev or display the previous page in the current screen
PF8 = Next or display the next page of the current screen

PF9 = Display the customizable options pop-up box. You may overtype the contents with the desired values and tap the Enter key to make the altered options active. Depending on the value in question, some apply to the user who entered the value and some apply to all users.

PF10 = Left or display the screen listed above this one in the Menu screen
PF11 = Right or display the screen listed below this one in the Menu screen

Note: The menu display is a two-up display and all Minimon multi-up displays fill each column from top to bottom before starting at the top of the next column.

PF12 = Help which displays the Menu screen

When is data actually collected by Minimon.

Batch data is collected from the first time the transaction MINI is used, until the next IPL. CICS transaction data is collected for every CICS partition after the first use of the transaction MINI after startup, in the CICS partition concerned, or from PLTPI time when an entry for MINIMON program exists in the PLTPI. CICS transaction data collection stops when the CICS online system is shutdown.

Minimon internal status display.

Enter the command:

MINI DIAG

to cause Minimon to display an internal status screen. The DIAG command will also refresh all entries from the MINIMON.CONFIG member.

There is also a Minimon console command (MM) that will allow the display of Minimon internal status information. It also allows the enabling/disabling of Minimon display options.

Enter the command:

MM

on the VSE console to see a list of supported commands and their functions.

Entering the command:

MM SET

on the VSE console will display a list of options that may be enabled/disabled via the console interface.

Note that MM accepts abbreviated commands and operands provided the number of characters entered provides sufficient characters to uniquely identify a command or operand.

Viewing CICS Application Trace Facility data.

As the quantity of data captured for this function can become formidable, this data is not written to the data collection log files. It is stored in memory, in compressed format, from transaction initiation till the transaction record is written to disk, and then the storage is released. To see this data, issue the command:

MINI DATA CLOSE

to manually close the data collection file so that the records are not written to disk, and so the ATF data storage information is not released. If the task is still executing, issue the command:

MINI TASK pt

where pt is the partition the CICS transaction is running in. If the task has finished executing, issue the command:

MINI TRAN pt

where pt is the partition the CICS transaction was run in. Place the cursor anywhere on the line showing the required transaction and tap the enter key. You will be taken to the ATFD screen showing the formatted ATF data. PF7 and PF8 may be used to page up and down the data.

You should issue the command:

MINI DATA OPEN

to reopen the data collection file when you have viewed the ATF data as while the file is closed transaction records are collected in memory, in a compressed format. Although the memory allocated for this buffer is sufficient for around 800 transactions before wraparound, and data loss, ATF and Database Clocking use a mimimum of 1K of GETVIS storage each in the CICS partition per CICS transaction. Reopening the data collection file allows this storage to be continuously reused.

Preventing MINIPRI and MINISEC (logging) from being used.

Do not supply labels for these two Sequential DASD datasets.


Viewing Third Party Product Support data.

As the quantity of data captured for this function can become reasonably large, this data is not written to the data collection log files. It is stored in memory, in compressed format, from transaction initiation till the transaction record is written to disk, and then the storage is released. To see this data, issue the command:

MINI DATA CLOSE

to manually close the data collection file so that the records are not written to disk, and so the ATF data storage information is not released. If the task is still executing, issue the command:

MINI TASK pt

where pt is the partition the CICS transaction is running in. If the task has finished executing, issue the command:

MINI TRAN pt

where pt is the partition the CICS transaction was run in. Place the cursor anywhere on the line showing the required transaction and tap the enter key. You will be taken to the ATFD screen showing the formatted ATF data. PF7 and PF8 may be used to page up and down the data. Now issue the command:

MINI TPPS

without specifying any partition id. You will be taken to the TPPS screen showing IBM and Third Party Database access counts for the transaction.

You should issue the command:

MINI DATA OPEN

to reopen the data collection file when you have viewed the ATF data, because while the file is closed transaction records are collected in memory in a compressed format. Although the memory allocated for this buffer is sufficient for around 800 transactions before wraparound, and data loss, ATF and Database Clocking use a mimimum of 1K of GETVIS storage each in the CICS partition per CICS transaction. Reopening the data collection file allows this storage to be continuously reused.

How to refresh the resource limits settings.

From a Minimon screen issue the Minimon command:

MINI DIAG

This will display Minimon internal diagnostic information, and also refresh all th eoptions and resource limits entered in the MINIMON.CONFIG library member.

When coding the resource limits specify specific tranids first followed by generic tranids. This will ensure selection of a specific resource limiting entry before a generic one. Generic tranids are specified by placing an asterisk in the tranid. e.g. ABC* or AB** to specify all tranids starting ABC or AB respectively.

When and how to run MINIVTM.

Minimon has three modes, in which it may be used.
1..As a CICS transaction 'MINI'
2..As a VTAM application, which may be logged onto 'MINIVTM'
3..As a dedicated 3270 terminal dedicated to MINIVTM

When running as a CICS transaction, MINIVTM is not required as CICS provides the required transaction environment for the Minimon CICS transaction 'MINI'.

When it is required to access Minimon without using the CICS transaction, for example when you do not have CICS running we supply our own transaction environment, MINIVTM, allowing the CICS transaction 'MINI' to be run under its control.

When required to run in an environment without VTAM, and perhaps without BTAM, MINIVTM will allow the use of a dedicated 3270 display. (See Starting and Stopping an assigned 3270 display above.)

MINIVTM is a VTAM application and as such required an entry in an application definition such as:

MINIVTAM VBUILD TYPE=APPL
IESWAITT APPL AUTH=(NOACQ)
MINIMON APPL AUTH=(PASS=ACQ)

A sample of this is supplied in member MINIAPPL.B in the distribution library.

If you have already placed the DLBLs for MINIPRI and MINISEC in system standard labels, you may remove the

// OPTION STDLABEL=DEL and // OPTION STDLABEL=ADD steps from the MINIVTM jcl supplied in MINIVTM.Z.

Note: If you run CA-DYNAM/D you must turn it off in the partition running MINIVTM. This may be done using the CA command:

SET DYNAMD=OFF

MINIVTM requires a parm to specify a small number of runtime parameters. The EXEC statement for MINIVTM takes the form of:

// EXEC MINIVTM,SIZE=264K,
                          PARM='APPLID=MINIVTM,SCAN=2,SIT=MM,TRACE=NO'

APPLID is the VTAM applid for MINIVTM defined in the APPL definition book.

SCAN is the terminal scan interval, in seconds, for a dedicated 3270 terminal only. 2 seconds has been found to be a reasonable delay. Specifying a shorter interval introduces unnecessary overhead. Specifying too long an interval leads to unacceptable wait time between pressing Enter on a Minimon display command and MINIVTM reading the terminal data.

SIT is the CICS SIT table suffix to be used to obtain the PCT and PPT tables for MINIVTM to use for its transaction processing. A set of pre-assembled SIT, PCT and PPT tables is supplied with suffixes of 'MM' so less storage is occupied than if you used your real CICS tables. Note that MINIVTM cannot access the CSD for these entries. Therefore if you use MINIVTM, and have migrated your PCT and PPT to the CSD you will need to use the Minimon pre-generated tables.

TRACE sets the MINIVTM internal trace option for debugging. It should be left as specified, due to its using increasing the overhead within MINIVTM.

To close a VTAM terminal session with MINIVTM issue the (CICS) transaction:

CSSF LOGOFF

To enter commands to the MINIVTM facility from the VSE console issue the VSE MSG command:

MSG xx

and then reply to the prompt with the command, or

MSG xx,DATA=...

The commands supported for MINIVTM are:
CHEK - test the program check recovery routine
DUMP - dump MINIVTM internal control blocks
END -- shutdown the MINIVTM facility
EXIT - display MINIVTM internal exit statistics
SEGM - segment MINIVTM SYSLST output
STOR - display MINIVTM storage utilization data
TRCE - display MINIVTM trace table entries
START=cuu - start a dedicated terminal on cuu
STOP=cuu - stop a dedicated terminal on cuu

Starting and Stopping a 3270 dedicated (assigned) display terminal.

This mode of running Minimon is available via the MINIVTM VTAM and dedicated terminal interface. Once the MINIVTM job is running, enter:

MSG pt

where pt is the partition syslog id of the MINIVTM job. A message will be issued by MINIVTM indicating it is ready for input. Enter:

replid START=cuu

or

replid STOP=cuu

where replid is the VSE reply id, and cuu is the address of the terminal.

Note: The terminal must not be assigned in any partition, including MINIVTM's before being started. MINIVTM will issue the assign for a start and issue the unassign for stop.

Minitms

Minitms is usually activated from within Minimon, but may be run as a stand-alone facility.

Minitms requires one VSAM KSDS for its catalog, and two VSAM ESDS for its log files.  The following JCL may be used, with suitable modifications, to define and initialize these datasets.
It is not neccessary to pre-initialize a newly defined MINICTL, as MINITMS will do this for itself th efirst time it needs to open MINICTL.

 
* $$ JOB JNM=MINITMS,CLASS=Z,DISP=K
* $$ LST CLASS=A,DISP=H
// JOB MINITMS
// SETPARM LIB='PRD4'
// SETPARM SLIB='LOCAL'
// LIBDEF PHASE,SEARCH=&lib..&sublib,TEMP
// LIBDEF SOURCE,SEARCH=&lib..&sublib,TEMP
/*
/* GOTO NOLABEL
// OPTION STDLABEL=DELETE
TMSCNTL
TMSLOGA
TMSLOGB
/*
// OPTION STDLABEL=ADD
// DLBL TMSCNTL,'MINIMON.TMSCNTL',,VSAM,CAT=IJSYSUC
// DLBL TMSLOGA,'MINIMON.TMSLOGA',,VSAM,CAT=IJSYSUC
// DLBL TMSLOGB,'MINIMON.TMSLOGB',,VSAM,CAT=IJSYSUC
/*
/. NOLABEL
/*
// EXEC IDCAMS,SIZE=AUTO
DELETE (MINIMON.TMSCNTL) CLUSTER PURGE CATALOG(VSESP.PROD.CATALOG)
DELETE (MINIMON.TMSLOGA) CLUSTER PURGE CATALOG(VSESP.PROD.CATALOG)
DELETE (MINIMON.TMSLOGB) CLUSTER PURGE CATALOG(VSESP.PROD.CATALOG)
DEFINE CLUSTER(NAME(MINIMON.TMSCNTL) -
  IXD -
  RECORDS(20 20) -
  RECSZ(80 123) -
  FREESPACE(0 0) -
  SHR(2) -
  VOLUMES(SYSWK3)) -
  DATA(NAME(MINIMON.TMSCNTL.DATA) -
  KEYS(45 0)) -
  INDEX(NAME(MINIMON.TMSCNTL.INDEX)) -
  CATALOG(VSESP.PROD.CATALOG)
DEFINE CLUSTER(NAME(MINIMON.TMSLOGA) -
  RECSZ(132 132) -
  RECORDS(20) -
  NIXD -
  REUSE -
  CISZ(4096) -
  SHR(2 3) -
  VOLUMES(SYSWK3)) -
  DATA(NAME(MINIMON.TMSLOGA.DATA)) -
  CATALOG(VSESP.PROD.CATALOG)
DEFINE CLUSTER(NAME(MINIMON.TMSLOGB) -
  RECSZ(132 132) -
  RECORDS(20) -
  NIXD -
  REUSE -
  CISZ(4096) -
  SHR(2 3) -
  VOLUMES(SYSWK3)) -
  DATA(NAME(MINIMON.TMSLOGB.DATA)) -
  CATALOG(VSESP.PROD.CATALOG)
/*
/&
* $$ EOJ

Minivtm

Use the following JCL as a sample
* $$ JOB JNM=MINIVTM,CLASS=Z,DISP=K
* $$ LST CLASS=A,DISP=H
// JOB MINIVTM
// SETPARM LIB='PRD4'
// SETPARM SLIB='LOCAL'
// LIBDEF PHASE,SEARCH=&lib..&sublib,TEMP
// LIBDEF SOURCE,SEARCH=&lib..&sublib,TEMP
/*
/* Note: To prevent MINIMON from opening, or using the log files,
/* simply do not provide the labels, as below, for MINIPRI and MINISEC.
/*
/* GOTO NOLABEL
// OPTION STDLABEL=DELETE
MINIPRI
MINISEC
/*
// OPTION STDLABEL=ADD
// DLBL MINIPRI,'MINIMON.MINIPRI',0,SD
// EXTENT SYSREC,SYSWK1,,,473600,2656
// DLBL MINISEC,'MINIMON.MINISEC',0,SD
// EXTENT SYSREC,SYSWK1,,,476256,2656
// OPTION USRLABEL
/*
/. NOLABEL
/*
// EXEC IESWAITT
/*
// SETPFIX LIMIT=20K
/*
// EXEC MINIVTM,SIZE=264K,PARM='APPLID=MINIVTM,SCAN=2,SIT=MM,TRACE=NO'
/*
/&
* $$ EOJ

Prtxfer

Use the following JCL as a sample
* $$ JOB JNM=PRTXFER,CLASS=Z,DISP=K
* $$ LST CLASS=A,DISP=H
// JOB PRTXFER
// SETPARM LIB='PRD4'
// SETPARM SLIB='LOCAL'
// LIBDEF PHASE,SEARCH=&lib..&sublib,TEMP
// LIBDEF SOURCE,SEARCH=&lib..&sublib,TEMP
// ASSGN SYS020,SYSLST
// SETPFIX LIMIT=4K
// EXEC PRTXFER,SIZE=AUTO
/*
/&
* $$ EOJ


VSAMmon

Use the following startup JCL as a sample
* $$ JOB JNM=VSAMMON,CLASS=Z,DISP=K
* $$ LST CLASS=A,DISP=H
// JOB VSAMMON
// SETPARM LIB='PRD4'
// SETPARM SLIB='LOCAL'
// LIBDEF PHASE,SEARCH=&lib..&sublib,TEMP
// LIBDEF SOURCE,SEARCH=&lib..&sublib,TEMP
// EXEC VSAMMON,PARM='VSAM'
/*
/&
* $$ EOJ

Use the following to start VSAMmon limiting DSNs handled to those starting with 'PROD' with no logging
* $$ JOB JNM=VSAMMON,CLASS=Z,DISP=K
* $$ LST CLASS=A,DISP=H
// JOB VSAMMON
// SETPARM LIB='PRD4'
// SETPARM SLIB='LOCAL'
// LIBDEF PHASE,SEARCH=&lib..&sublib,TEMP
// LIBDEF SOURCE,SEARCH=&lib..&sublib,TEMP
// EXEC VSAMMON,PARM='VSAM,N,PROD'
/*
/&
* $$ EOJ

Use the following to start VSAMmon limiting DSNs handled to those starting with 'PROD' with logging to DMF
* $$ JOB JNM=VSAMMON,CLASS=Z,DISP=K
* $$ LST CLASS=A,DISP=H
// JOB VSAMMON
// SETPARM LIB='PRD4'
// SETPARM SLIB='LOCAL'
// LIBDEF PHASE,SEARCH=&lib..&sublib,TEMP
// LIBDEF SOURCE,SEARCH=&lib..&sublib,TEMP
// EXEC VSAMMON,PARM='VSAM,L,PROD'
/*
/&
* $$ EOJ

Use the following shutdown JCL as a sample
* $$ JOB JNM=VSAMMON,CLASS=Z,DISP=K
* $$ LST CLASS=A,DISP=H
// JOB VSAMMON
// SETPARM LIB='PRD4'
// SETPARM SLIB='LOCAL'
// LIBDEF PHASE,SEARCH=&lib..&sublib,TEMP
// LIBDEF SOURCE,SEARCH=&lib..&sublib,TEMP
// EXEC VSAMMON,PARM='VSAM,DEL'
/*
/&
* $$ EOJ

Note that $JOBAC05 (VSAMMON) is always enabled when VSAMMON runs, and cannot be explicitly enabled/disabled with the commands below.

Enter the command:

MM JOBA

to display a $JOBACCT exit status list on SYSLOG.

MM JOBA ENA n exitname

to enable a $JOBACCT exit. The phase $JOBAC0n (where 'n' is the exit number) must be preloaded in the SVA. 'exitname' is a user-friendly name for the exit.

MM JOBA DIS n exitname

to disable a $JOBACCT exit. 'exitname' is a user-friendly name for the exit.

MM JOBX

to display a $JOBEXIT exit status list on SYSLOG.

MM JOBX ENA n exitname

to enable a $JOBEXIT exit. The phase $JOBEX0n (where 'n' is the exit number) must be preloaded in the SVA. 'exitname' is a user-friendly name for the exit.

MM JOBX DIS n exitname

to disable a $JOBEXIT exit. 'exitname' is a user-friendly name for the exit.

MM OPEN pt

to display all open VSAM datasets in partition pt on SYSLOG. Current I/O counts and VSAM CPUTIME is also displayed.

MM OPEN dsn

to display all partitions with the dataset name beginning with the entered dsn, or part of a dsn, on SYSLOG. Current I/O counts and VSAM CPUTIME is also displayed.

Some exit status information is only available for exits coded to allow the status display to show extended information.

Bugs, questions, suggestions ?

Please contact us via e-mail at

 

Back Next
Copyright 2003 - 2005 The Minimon People. All rights reserved