 |
Dbugpgm
Online, realtime Batch and CICS debugger for
Assembler and COBOL. |
|
 |
|
|
Despool
POWER LST queue entry copier to DASD, VSE library,
TAPE, OS/2 file or VSAM ESDS. |
|
|
|
|
Minimon
Realtime CICS and VSE performance monitor.
Additionally, provides a native MVS program
execution environment. |
|
|
|
|
|
Minitms
A part of Minimon that provides a simple Tape
Management System. |
|
|
|
|
|
Minivtm
A part of Minimon that simulates a limited command
and macro level CICS facility. |
|
|
|
|
|
Prtxfer
Utility to transfer VM PRT queue entries to the VSE
POWER LST queue. |
|
|
|
|
|
VSAMmon
Stand-alone multiple $JOBACCT facility with VSAM
file monitoring capability |
|
|
|
|
 |
Common Product Install
Procedure
All our products and utilities are supplied in a common format
The 6 common steps below will catalog the product or utility on
your system
Please start with the following 6 steps...
The product distribution file contains 1 VSE job within 1 POWER
job
Unzip this distribution file
Upload the unzipped file to the POWER RDR queue (Binary
Lrecl 80 Recfm F
Run this uploaded POWER job
The job will prompt you for the target VSE library and
sublibrary names
Punch out any .B and .Z members just cataloged - they contain
samples and JCL
Uploading the unzipped file to the POWER RDR queue.
From a PC-based 3270 session, sign-on to the Interactive User Interface. Select
'Operations', 'Personal Computer Move Utilities', 'PC File Transfer'. You should then see
the message 'Please switch to PC mode to initiate a file transfer or press PF3 to quit'.
Switch to PC mode and enter the PC command:
For VSE/ESA releases before 1.3.0:
SEND jobname.jcl jobname (LRECL=80 BINARY
This will transfer the product installation jcl file to the Host Transfer File with the name of
jobname. Once complete switch back to host mode. Select 'Operations', 'Personal Computer
Move Utilities', 'Move Files from Host Transfer File to ICCF'. Move the newly uploaded
file into an ICCF library member. Then you can submit it to power using your usual submit
procedure.
For VSE/ESA 1.3.0 or higher:
SEND jobname.jcl (LRECL=80 BINARY FILE=RDR
Note: These directions assume you have changed the PC directory to that in which you unzipped
the product installation jcl. The command format may have to be modified to conform to the requirements of
your particular 3270 terminal emulator.
Now continue with those steps below applicable to the
specific product or utility
Dbugpgm
Add the following entries to your CICS CSD:
CEDA DEF GROUP(DBUG) PROG(DBUGPGM) LANGUAGE(ASSEMBLER)
CEDA DEF GROUP(DBUG) TRANS(DBUG) PROGRAM(DBUGPGM)
Install the group just added:
CEDA INST GROUP(DBUG)
See our Support page for instructions on using
Dbugpgm
Despool
See our Support page for instructions on using
Despool
Minimon
Add the following entries to your CICS CSD:
CEDA DEF GROUP(MINI) PROG(MINICAB) LANGUAGE(ASSEMBLER) EXECKEY(USER)
CEDA DEF GROUP(MINI) PROG(MINIMON) LANGUAGE(ASSEMBLER)
EXECKEY(CICS)
CEDA DEF GROUP(MINI) TRANS(MINI) PROGRAM(MINIMON)
Install the group just added:
CEDA INST GROUP(MINI)
To automatically start Minimon in CICS, MINIMON may be added
to the PLTPI:
DFHPLT TYPE=ENTRY,PROGRAM=MINIMON
To stop the long-running Minimon service task in CICS, MINIMON
may be added to the PLTSD in the first stage (before the
entry for DFHDELIM):
DFHPLT TYPE=ENTRY,PROGRAM=MINIMON
For CICS/TS, CICS Monitoring must be enabled for Minimon to create
its transaction records:
DFHSIT MN=ON,MNPER=ON
Locate DASD space for the two data collection files, if not
using DMF:
MINIPRI and MINISEC DASD labels:
These two labels must be placed in System Stsndard Labels, only when you
wish to collect data for later batch reporting via MINIREP.
// 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
The properties for the MINIPRI and MINISEC data collection
files are:
- DTFSD
- RECFORM=FIXUNB
- For an input DTFSD, specify BLKSIZE=216
- For an output DTFSD, specify LRECL=216 and BLKSIZE=224
- For CKD, as many 216-byte records as will fit per track are written
- For FBA, two (2) 216-byte records are written per FBA block
- Data is uncompressed fixed format records
- Records are written in chronological order: at end of Batch job
step and end of CICS task
Notes:
These two labels must be for sequential disk extents.
VSAM ESDS or VSAM/SAM cannot be used.
Do not use a DASD manager to allocate these extents.
The extents should be adjusted accordingly for your DASD and system usage.
Due to the use of SYSREC, these single extent files must be allocated on SYSWK1.
Storage requirements:
SVA 31-bit: 428K
SVA 24-bit: 40K
SVA GETVIS 31-bit: 255K
SVA GETVIS 24-bit: 61K
CICS: 80K
Minivtm: 133K plus 4K in 24-bit SVA
If 31-bit SVA is not available, Minimon will try to use 24-bit SVA.
Minimon loads all its own phases into the non-Getvis SVA.
These phases should NOT be pre-loaded via 'SET SDL'.
Local configuration member: MINIMON.CONFIG
An example MINIMON.CONFIG options member is supplied with the product as
a member called MINIMON.CONFIG in the installation VSE
library.sublibrary.
This member should be punched out via LIBR, reviewed
for applicability, and then cataloged in the VSE PRD2.CONFIG
sublibrary.
See our Support page for instructions on using
Minimon
Minitms
See our Support page for instructions on using
Minitms
Minivtm
See our Support page for instructions on using
Minivtm
Prtxfer
See our Support page for instructions on using
Prtxfer
VSAMmon
See our Support page for instructions on using
VSAMmon
|
|
 |
