Method-level debugging with COD0

Start of changeAfter logging onto CICS®, enter the COD0 transaction ID to display the COD0 main menu. Figure 22 shows the COD0 main menu displayed under CICS/ESA, and CICS/MVS™.

Figure 22. COD0 debugging transaction menu (CICS/ESA, and CICS/MVS)
Start of change COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 Welcome to CICSPlex/SM Debugger. Commands available are:
 
      ALLOC       Allocate storage, cache, cache list, queue, or eptr.
      ATTACH      Starts a method running in MAS/CMAS.
      CALL        Call a CICS transaction or program.
      CAPTURE     Capture an EUI View to print.
      DUMP        Call CODB transaction to display memory.
      EXEC        Executes a method immediately from the debugger.
      EXIT        Exit the debugger.
      LIST        List methods, CP/SM tasks, and resources.
      POST        Posts an ECB using MVS POST.
      PRINT       Print a CP/SM data area to the JES Spooler.
      PURGE       Delete a resource ALLOCated.
      START       Starts a method running in CMAS.
      TRACE       Set CICS component trace flags.
      TRACK       Set CPSM trace flags based on calling structure.
      TRAP        Set tracing flags for a single method.
 
  Enter HELP (command) for more help on commands.End of change

To issue a COD0 debugging command, enter it in the CMD=> input field. Commands can include one or more parameters, which must be separated by one or more spaces. Commas and quoted strings are not supported.End of change

As in ISPF, PF key functions are prefixed to whatever is on the command line. The following PF keys are in effect when COD0 is running in a CICS/ESA, or CICS/MVS, environment:

Start of change
Key
Description
PF1
HELP
PF3
END
PF4
PREV
PF5
NEXT
PF7
UP
PF8
DOWN
End of change

Issuing commands recursively

Start of changeYou can enter the debugger commands recursively from any screen in the COD0 transaction, effectively nesting the commands and their output. However, under CICS/ESA, and CICS/MVS, when the LIST and HELP commands are entered recursively, the new output replaces the old. For example, if you issue the LIST START command followed by the LIST TASK command, the LIST TASK output replaces the LIST START output.End of change

Issuing commands that alter CICSPlex SM

Start of changeThe following COD0 debugging commands can be used to modify memory or some other aspect of CICSPlex® SM operation:

When you issue one of these commands, you receive a warning and confirmation panel. You should proceed with the command only at the request of customer support personnel.End of change

ALLOC (allocating a resource)

Start of changeThe ALLOC command allocates a resource so that you can refer to it by name in completing MALs. The resource can be a cache list, a data queue, data space storage, or shared CICS storage.End of change

The format of the ALLOC command is:

ALLOC /resname [optional parameters...]

where:

/resname
Identifies the resource being allocated. The resource name can be no more than eight characters, including the required slash.

The optional parameters are:

QUEUE compid
Creates a queue token and assigns it to the resource being allocated. compid is the 3-character component identifier, as listed in Major components of CICSPlex SM.
CLIST
Displays the Allocate CACHE LIST input panel (shown in Figure 23), which lets you create a CACHE LIST token and assign it to the resource being allocated.
STG size [BELOW]
Acquires an address of the specified size from CICS shared storage and assigns it to the resource being allocated. size is a number of bytes. The BELOW option requests storage from below the 16MB line; by default, storage is acquired above the line (in 31-bit mode).
EPTR size
Acquires a data space pointer of the specified size from a data space and assigns its ALET and OFFSET to the resource being allocated. size is a number of bytes.
Figure 23. Allocate CACHE LIST panel
COD0 CICSPlex/SM Debugger
CMD=>                                                            Scroll=> PAGE
 
Allocate CACHE LIST
 
     Id of CACHE to create CACHE LIST: /@CACHE           (Optional)
 
     Estimated number of elements:
 
     Element size:
 
     Estimated free space:        (Optional)
 
     GENERIC if generic keys:          (Optional)
 
     Hash Table Size:        (Optional)
 
     Key Offset: 0      (Default 0)
 
     Key Size:
 
     Search method (BINSRCH/HASH): BINSRCH
 

Resources remain allocated across multiple COD0 transactions or between multiple COD0 transactions running concurrently in the same CICS system. In fact, all resources exist until you specifically purge them.

Notes:
  1. You can use the LIST ALLOC command to display a list of allocated resources.
  2. You can use the DUMP /resname command to dump the storage, data queue, or cache list for an allocated resource.

ATTACH (attaching a method)

Start of changeThe ATTACH command starts a method running in the CICS systems identified by the specified context and scope values.End of change

The format of the ATTACH command is:

ATTACH method context scope

where:

method
Is the ID of a CICSPlex SM method that has been coded to run from a CICSPlex SM end-user interface request.
context
Is the name of a CMAS or CICSplex.
scope
Is the name of a CICSplex, CICS system group, or CICS system.

For a list of valid responses to this command, see Running a method.

Start of changeUnlike the START command, which merely starts a CICS transaction within a CMAS, ATTACH crosses the boundary between a CMAS and a local MAS. (These methods may run in the CMAS, a different address space, or even a different processor in the CICSplex). To accomplish this, ATTACH uses the logic of an end-user interface request, which runs under its own TCB in the CMAS.End of change

Figure 24 is an example of the display for a completed attached task that ran within a single CMAS or MAS.

Figure 24. Attached task display for a single CMAS or MAS
Start of changeCOD0 CICSPlex/SM Debugger
CMD=>                                                            Scroll=> PAGE
Enter END to exit or ENTER to view results.
Status for ATTACHed method  XQCQ
 
       Methods status:  Method completed.
       XLCI return description:  OK
       Method's RESPONSE was:    OK
       Method's REASON was:
 
       CONTEXT:  CVMCTSO1   SCOPE:  CSYSGRP1   REGION:  CSYSGRP1
 
       Unit of work
          SYSID:  TEST     USERID:  DEVOPER  TCB  00452160
          Major Object:  00   Component Id:  73
 
 
       The method executed in a single MAS so all information
       appears in the fields of the MAL.
 End of change

Figure 25 is an example of the display for a completed attached task that either ran in multiple MASs, or ran multiple times in a CMAS.

Figure 25. Attached task display for multiple CMASs or MASs
Start of changeCOD0 CICSPlex/SM Debugger
CMD=>                                                            Scroll=> PAGE
Enter END to exit or ENTER to view results.
Status for ATTACHed method  XQCQ
 
       Methods status:  Method completed.
       XLCI return description:  OK
       Method's RESPONSE was:    OK
       Method's REASON was:
 
       CONTEXT:  CVMCTSO1   SCOPE:  CSYSGRP1   REGION:  CSYSGRP1
 
       Unit of work
          SYSID:  TEST     USERID:  DEVOPER  TCB  00452160
          Major Object:  00   Component Id:  74
 
       The method executed in multiple MAS so a queue of OUT records
       was created.
 
       OUTQUE QUEUE ID:  A4957FBD B3E11932
                    Records :  0000013  Record Length:  0000018
 End of change

When you press Enter, each of the MALs that ran in each region is reconstructed and displayed individually, as shown in Figure 26.

Figure 26. MAL display for a specific CICS region
COD0 CICSPlex/SM Debugger
CMD=>                                                            Scroll=> PAGE
NEXT/PREV to browse CICS region MALS. END=Exit.
MAL for CICS Region:CICSSY01
IN
   *ENM FUNCTION( CREQUE )
    CHR DEBUG(          )
    PTR ECB( 00000000 )
   *CMP MAJOR_OBJECT( KNL )
   *ENM TYPE( WORK )
   *SDT DELETE( TRUE  )
OUT
   *ENM RESPONSE( OK )
   *ENM REASON(                    )
   *ETK QTOKEN( A4957FC53998FB31 )
 

Note also that the region the MAL ran in is shown on the header line for the display. You can use the NEXT (PF5) and PREV (PF4) keys to browse backwards and forwards between the regions. END (PF3) returns you to the attached task display.

CALL (calling external CICS programs and transactions)

Start of changeThe CALL command calls a CICS transaction or program with optional parameters.End of change

The format of the CALL command is one of the following:

CALL cicstran [optional parameters...]
 
CALL PROGRAM cicsprog [optional parameters...]
Note:
CICS can be used as a synonym for CALL.

cicsprog
Is a program ID that must be defined to CICS.
cicstran
Is a transaction ID that must be defined to CICS.

The parameters are passed as a TIOA area, so anything that can be entered at the transaction’s or program’s initial screen can be specified as an optional parameter. There is no validation of the optional parameters.

For transaction calls, the transaction ID is placed as the first field in the constructed TIOA (as it would be from the terminal). Make sure the transaction is defined as conversational. Pseudo- or nonconversational programs return immediately to COD0.

For program calls, you must enter the transaction ID as the first parameter, if the program you are calling expects this.

While the task is running, all the facilities of that CICS transaction or program are available to you. When you end the task, you return to COD0.

Note:
You should not attempt to call:

CAPTURE (capturing and printing a view)

The CAPTURE command captures and prints all communications related to a CICSPlex SM end-user interface view being issued by a particular user. CAPTURE uses the CICS spool facility to write the data as an output file called Sxxxxxxx, where xxxxxxx is a numeric identifier.

The format of the CAPTURE command is one of the following:

CAPTURE viewname userid count
 
CAPTURE *MASMON montype count

where:

viewname
Is the name of the CICSPlex SM view to be captured.
userid
Is the TSO user ID of the user who will be issuing the view command.
count
Is the number of times the view should be captured.

A count is taken from the time the view command is entered until the user enters another view command or END. Pressing Enter repeatedly to refresh the data or perform some action against the view does not change the count of the view command.

You can reissue the CAPTURE command with the same view name and user ID to update the count. A count of zero deletes the CAPTURE entry.

*MASMON
Captures monitor data as it is collected by a MAS.
montype
Is the type of monitor data to be captured:
MCICS
CICS regions
MCONN
Connections
MDBX
DB2® and DBCTL resources
MFILE
Files
MGLBL
Global resources
MJRNL
Journals
MPROG
Programs
MTDQS
Transient data queues
MTERM
Terminals
MTRAN
Transactions

For example:

CAPTURE MONDEF USER39 3

captures the next three MONDEF view commands issued by USER39. All related MALs and queues are printed.

DUMP (displaying and altering data)

Start of changeThe DUMP command displays a scrollable dump of memory. Some parameters of the DUMP command cause the CICSPlex SM system-level debugging transaction, CODB, to be invoked.End of change

If you alter the displayed memory, you must enter UPDATE (or press PF11) to record the change. If you alter memory but do not enter UPDATE, a message is displayed to remind you to enter UPDATE.

The format of the DUMP command is:

DUMP [parameters...]

where the parameters are:

/resname
Start of changeDisplays the queue, EPTR, storage, or cache list allocated to the specified resource.End of change
@method
Calls CODB with the entry point of the specified CICSPlex SM method.
hexadecimaladdress
Start of changeAssumes the hexadecimal value is an address and enters CODB with ALET=0 and the address specified.End of change
hexadecimalALET hexadecimaloffset
Start of changeDisplays the address of the specified ALET (first hexadecimal value) at the specified offset (second hexadecimal value).End of change
hexadecimaladdress [length]
Start of changeDisplays the storage starting at the specified address. The amount of storage displayed is determined by the length parameter. Length is assumed to be a decimal value, unless a X'length' value is specified.End of change
CACHE cachetoken
Start of changeDisplays the data identified by the specified cache-list token. The token is entered as two 8-byte hexadecimal character strings. To display the previous record, use PF4; to display the next record, use PF5; to display a specific record, enter REC n, where n is the record number.End of change
CLIST token
Start of changeCalls CODB with the specified token. The token is entered as two 8-byte hexadecimal character strings.End of change
EIB compid
Start of changeDisplays the address of the CICS information block for the first transaction running under the specified component.End of change
EIS compid
Start of changeDisplays the address of the CICS storage block for the first transaction running under the specified component.End of change
MODB compid
Displays the address of the MODB for the specified component.
MODD
Start of changeDisplays the address of the MODD.End of change
MOEB compid
Displays the address of the MOEB for the specified component.
OPB compid
Start of changeDisplays the address of the first OPB for the specified component.End of change
QUE token
Start of changeDisplays the data identified by the specified token. The token is entered as two 8-byte hexadecimal character strings.End of change
STAKEND compid
Start of changeDisplays the address of the last stack for the first transaction running under the specified component.End of change
STAKSTRT compid
Start of changeDisplays the address of the initial stack for the first transaction running under the specified component.End of change
XLWA
Displays the CICSPlex SM kernel linkage work area.

Figure 27 shows an example XLWA display.

Start of changeStart of changeFigure 27. An example DUMP XLWA displayEnd of change
COMMAND==> XLWA       COMP ID==>      ADDR==>           ALET==> 00000000     
MSG==>                                                                       
0012D0A8  00000000  08006EC5  E8E4D5E7  D2D5D3C3  E6C1C1C2  ..>EYUNXKNLCWAAB 
0012D0B8  00000010  0D000200  00000000  00000000  00000000  ................ 
0012D0C8  00000020  8001608B  0000000E  0000EE00  11F20000  ..-..........2.. 
0012D0D8  00000030  0012D168  0000DE5C  113E8000  00000546  ..J....*........ 
0012D0E8  00000040  116D4468  00040000  11F2EE00  00100000  ._.......2...... 
0012D0F8  00000050  11F2EE00  FFFFFF6A  00000000  00000000  .2.....|........ 
0012D108  00000060  00000000  D2D3D7C2  116D8EB0  116DB328  ....KLPB._..._.. 
0012D118  00000070  116D7728  00CA812C  00000000  00000000  ._....a......... 
0012D128  00000080  00000000  00000000  00000000  00346EC5  ..............>E 
0012D138  00000090  E8E4E7C5  C5E8E4D9  E7C5D3E2  01030000  YUXEEYURXELS.... 
0012D148  000000A0  00CC4008  0E1B9CE8  00CA8118  00CA812C  .. ....Y..a...a. 
0012D158  000000B0  00F69A00  009C9520  0000011C  00000001  .6....n......... 
0012D168  000000C0  00000000  11F20000  11F21100  11F22200  .....2...2...2.. 
0012D178  000000D0  11F23300  11F24400  11F25500  11F26600  .2...2...2...2.. 
0012D188  000000E0  11F27700  11F28800  11F2AA00  11F29900  .2...2h..2...2r. 
0012D198  000000F0  11F2BB00  11F2CC00  00000000  00000000  .2...2.......... 
0012D1A8  00000100  11F2DD00  00000000  00000000  00000000  .2.............. 
0012D1B8  00000110  00000000  00000000  00000000  00000000  ................ 
0012D1C8  00000120  00000000  00000000  00000000  00000000  ................ 
End of change
Notes for CICS/ESA, and CICS/MVS, users:
  1. If you issue the DUMP command without parameters, the CODB main menu is displayed.
  2. For CICSPlex SM components, CODB displays the first transaction running under that component, which is its first OPB. You can use the NEXT and PREV PF keys to display multiple transactions. You can also use the LIST TASK command to display all of the stacks and methods in all of the CICSPlex SM tasks, and then select specific stacks, methods, or OPBs to display.

EXEC (executing a method)

The EXEC command executes a method directly from the COD0 debugging transaction.

The format of the EXEC command is:

EXEC method

where:

method
Is the name of a CICSPlex SM method.

The formatted message argument list (MAL) for the method is displayed. For details about how to enter data from this display, see Displaying a MAL from COD0. For a list of valid responses to this command, see Running a method.

EXIT (exiting COD0)

The EXIT command exits the COD0 debugging transaction. This command has no parameters.

You can use this command to exit the debugging transaction from any screen. A closing message is displayed; you can then clear the CICS screen and enter another transaction.

Note for CICS/ESA, and CICS/MVS users:

All allocated resources and started or attached tasks are recorded in a temporary storage record. The next time you enter COD0, all allocated resources are still available and all started or attached tasks can be displayed using the LIST START command.

HELP (getting online help)

The HELP command displays help text for COD0 commands.

The format of the HELP command is:

HELP [cmdname | COMPID]

where:

cmdname
Is the COD0 command for which help information is to be displayed.
COMPID
Produces a list of identifiers of CICSPlex SM components.

If you issue the HELP command without parameters, the initial help panel, which lists all COD0 commands, is displayed.

LIST (listing tasks and allocated resources)

The LIST command lists running CICSPlex SM tasks, the status of started and attached tasks, and the allocated resources available to you.

The format of the LIST command is:

LIST [parameters...]

where the parameters are:

ALLOC
Start of changeLists all allocated resources. You can purge or dump resources from this screen.End of change
ATCB
Lists the API task control blocks used for processing CICSPlex SM API requests.
CACHE
Start of changeLists the data caches in use by a local MAS.End of change
CAPTURE
Start of changeLists all ISPF end-user interface views currently being captured.End of change
CLIST
Start of changeLists the data cache lists in use by a CMAS.End of change
COMM
Start of changeLists the two communication MAL queues: one for methods executing via the CMAS, and the other for methods routed to a MAS.End of change
DLL [TASK cicstaskid |PID processid]
Start of changeLists dynamic link libraries (DLLs) for the all CICSPlex SM components loaded for a process. By default, the details are for the DLLs loaded for the process running the CONL transaction. However, on some operating systems these are not guaranteed to be the same for all processes. To display details for another process, specify either the CICS task ID or the operating system process ID.End of change
METH [compid]
Lists all methods within the specified component. If no component is specified, all methods are listed.
START
Start of changeLists all started and attached tasks and their current status. You can purge, display, or dump the MAL created from this screen as well as restart, attach, or execute the same MAL.End of change
STCB [ERRORS]
Start of changeLists the server-client control blocks. The ERRORS option provides a description of any errors encountered.End of change
TASK [compid]
Lists the CICSPlex SM tasks from the specified component showing all active method calls. If no component is specified, all tasks are listed.
VIEWS [mask]
Start of changeLists all ISPF end-user interface views that can be captured. The mask option is a generic key that can be used to qualify the list.End of change
Note:
You must issue END or CANCEL to terminate a LIST task.

LIST ALLOC

Lists all the resources that have been allocated by the ALLOC command. Figure 29 shows an example of the LIST ALLOC display.

Figure 28. An example LIST ALLOC display
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 Select P=Purge resource  D=Dump resource
 S Type  Name     Token             Length MajObj
 _ CACHE /@CACHE  01FF0004 000026E0
 _ QUE   /QUE     A44C5E58 27257332       MAS
 _ CLIST /C       000026E0 00106DF8   256
 _ STG   /STG     00000000 04289000  4096
 _ EPTR  /E       01FF0005 00001B00  2048

The fields on this display are:

Field
Description
Type
The type of resource, as one of the following:
EPTR
Data space pointer
CLIST
Cache list
CACHE
Cache
STG
CICS storage
QUE
Queue ID
Token
The 4-byte address or 8-byte token broken into two fullwords (ALET first).
Length
The size of allocated storage or the element length for a cache list.
MajObj
The major object, or component, used when allocating.

You can enter the following in the selection field:

Command
Description
P
Purges the resource.
Note:
You cannot purge /@CACHE, which is the cache created by COD0.
D
Enters CODB and dumps the resource. This is the same as entering DUMP /resname on the command line.

Start of change

LIST ATCB

LIST ATCB lists the API task control blocks. These control blocks are used when a CICSPlex SM API operation is in progress.

Figure 29. An example LIST ATCB display
 COD1 CICSPlex/SM Debugger                       APPLID=IYEGZGC0
       CMD=>                                             Scroll=> PAGE
       D=Dump ATCB  C=Dump CMDDesc  T=Task  END=Exit.
       S ATCB     Status   Task# Cmd  Origin        DispTime APITime
       _ 164B82B0 Active *  6337 GET_ IYEGZGW0/7186 00:00.00 00:32.93
       _ 164B78D0 Avail  *  6344
       _ 164B5ED0 Free
       _ 164B58D0 Free
       _ 1649EED0 Free
       _ 1649ECB0 Free
                Total API Commands:           114,842

The fields on this display are:

Field
Description
ATCB
The address of the ATCB control block
Status
The status of the control block, as one of the following:
Active
An API request is being processed.
In Use
An API request has been queued for processing.
Avail
Available and waiting for work.
Free
Available, but not waiting for work.
Task#
The CICS task number.
Cmd
The CICSPlex SM API command being processed. This field is displayed only when Status=Active.
Origin
For CICS based requests, Origin is in the form: aaaaaaaa/nnnnn where aaaaaaaa is the CICS APPLID and nnnnn is the CICS task number making the CICSPlex SM API request being processed.

For non-CICS based requests, Origin is the MVS jobname of the address space making the CICSPlex SM API request being processed.

This field is displayed only when Status=Active.

DispTime
The elapsed time it took to dispatch the current API request.

This field is displayed only when Status=Active.

APITime
The elapsed time is has taken to process the current API request (Dispatch time not included).

This field is displayed only when Status=Active.

The Total API Commands line displays the count of CICSPlex SM API commands that have been processed by all ATCBs.

Command
Description
D
Dumps the ATCB
C
Dumps the API Command Descriptor if it is available.
T
Displays LIST TASK output for the CICS task processing the ATCB.
End of change

LIST CACHE

Start of changeLists the data caches in use by a local MAS. Figure 30 shows an example of the LIST CACHE display.

Figure 30. An example LIST CACHE display (CICS/ESA, CICS/MVS)
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 D=Dump lowest ALET:X'1000'
 S Cache    ALET     Low Ofs  High Ofs   HWM Allocated (Hex)
 _ DMDSCWW1 01FF001B 00000000 00801000       4,229,376 (00408900)
 _ WLM1CWW1 01FF0007 00000000 00400000       3,543,040 (00361000)
 _ RTA1CWW1 01010042 00000000 00400000         524,288 (00080000)
 _ MON1CWW1 01010041 00000000 00400000         524,288 (00080000)
 _ TOP1CWW1 01FF0006 00000000 00400000         655,360 (000A0000)
 _ COM1CWW1 01010040 00000000 00400000       1,691,648 (0019D000)
 _ MAS1CWW1 01FF0008 00000000 00400000         933,888 (000E4000)
 _ DAT1CWW1 0101003F 00000000 00400000       1,527,808 (00175000)
 _ QUE1CWW1 01FF0005 00000000 00400000       1,048,576 (00100000)

The fields on this display are:

Field
Description
Cache
The name of the data cache.
ALET
The ALET of the data cache.
Low Ofs
The lowest offset allocated, which should always be X'00000000'.
High Ofs
The highest offset within the data cache allocated.
HWM Allocated
The number of bytes of the data cache actually in use.
(Hex)
The HWM Allocated value expressed in hexadecimal.

Figure 31 shows an example of the LIST CACHE display.

Start of changeFigure 31. An example LIST CACHE display (CMAS )End of change
DBG0 CICSPlex/SM Debugger                                Applid:CICSWIN
  CMD=>                                                           Scroll=> PAGE
  _ Token             ElemLen Keylen Keyoff Records MaxRecs FreeRec    Storage
  _ 00000001-0123FA2C     300      5      0       3      10       1        760

The fields on this display are:

Field
Description
Token
The cache list token.
ElemLen
The length of the element.
Keylen
The length of the key.
Keyoff
The offset of the key in each record.
Records
The number of records in the cache.
MaxRecs
The maximum number of records the cache can hold before being expanded.
FreeRec
The number of free slots available.
Storage
The total storage size, including any overhead.
End of change

You can enter the following in the selection field:

Command
Description
D
Dumps the cache list data. This is the same as entering DUMP CACHE cachetoken on the command line.

LIST CAPTURE

Lists all ISPF end-user interface views currently being captured. Figure 32 shows an example of the LIST CAPTURE display.

Figure 32. An example LIST CAPTURE display
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 Enter END to exit.
 ViewName  User ID  Count  Debug  AltDebug  Desc
 FILES     CVMCW2       2  OT     NT        File Summary
 LOCFILE   CVMCW2       2  O8     N8        Local Files

The fields on the LIST CAPTURE display are:

Field
Description
ViewName
The name of the view for which data is being captured.
User ID
The TSO user ID from which the view command is being issued.
Count
The number of remaining times to capture the view.
Debug
The end-user interface program ID (that is, the selector) for the view being captured.
AltDebug
The back end program ID (that is, the action) for the view being captured.
Desc
A description of the view being captured.

LIST CLIST

Lists the data cache lists in use by the CMAS. Figure 33 shows an example of the LIST CLIST display.

Figure 33. An example LIST CLIST display
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 D=Dump the Cache List
 S Token            DataAlet DataStrt DataEnd  EleSz ElemCnt Key Len T S Alt
 _ 01FF001B00408990 01FF0007 00071000 00073C00    20       0   0  16 S B YES
 _ 01FF001B00408830 01FF0007 0016E000 00177E5C    72       0   0  16 S B YES
 _ 01FF001B004086D0 01FF0007 00165000 0016DCC4    64       0   0  16 S B YES

The fields on this display are:

Field
Description
Token
The cache list token.
DataAlet
The ALET of the cache list’s data.
DataStrt
The starting offset within the ALET allocated to the cache list.
DataEnd
The highest offset within the ALET allocated to the cache list.
EleSz
The size of each cache list element.
ElemCnt
The number of elements in the cache list.
Key
The offset of the key within an element.
Len
The length of the key.
T
The type of cache, as either standard (S) or generic (G).
S
The search type for the cache, as either binary (B) or hash (H).
Alt
Indicates whether there is an alternate index cache available.

LIST COMM

Lists the two communication MAL queues: one for methods executing via the CMAS, and the other for methods routed to a MAS. Figure 34 shows an example of the LIST COMM display.

Figure 34. An example LIST COMM display
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 S CSFM MAL      XLTD     Type     Node Type  Target  SysId Sequence
 Response List for:  MAL List
 _ TSQO 001ABC00 00E1E300 Outbound Local MAS  CMAS1AB  CAB1 00000012
 

The fields on this display are:

Field
Description
Response List for:
MAL List
MAL execution to or from a CMAS.
MAS List
MAL execution to or from a MAS.
CSFM
The method ID for the MAL being run.
MAL
The address of the relocated MAL.
XLTD
The address of the MAL descriptor table in the CMAS.
Type
The type of communications in progress:
Inbound
The MAL is being run locally from another CMAS.
Outbound
The MAL is being sent to another CMAS.
Response
The MAL response is being transferred.
Node Type
The type of node involved in the transfer:
CMAS
From a CMAS.
Local MAS
From a MAS in the same MVS image.

LIST METH

Start of changeLists all methods within the specified component. Figure 35 shows an example of the LIST METH display typical of those produced under CICS/ESA, and CICS/MVS.

Figure 35. An example LIST METH display (CICS/ESA, CICS/MVS)
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 L=Dump Load Pt  END=Exit.
 S Typ Meth Function Fmt Tran LoadPt   ServLevl Assembly Date  Status
 _ PUB CWAA ADDTMED  01       077130C0 CPSM210  05/19/98 06.05 ACTIVE
 _ PUB CWAB BROTMED  02       07713348 CPSM210  05/19/98 06.05 ACTIVE
 _ PUB CWAD DELTMED  03       077138F0 CPSM210  05/19/98 06.05 ACTIVE
 _ PUB CWAU UPDTMED  04       07713B40 CPSM210  05/19/98 06.05 ACTIVE

The fields on this display are:

Field
Description
Typ
The type of method, as either public (PUB) or private (PRV).
Meth
The method ID.
Function
The function name of the method.
Fmt
The format ID of the method.
Tran
If the method runs asynchronously, the CICS transaction ID used.
LoadPt
The load point of the method in memory.
ServLevl
The service level, or release level, of the method.
Assembly Date
The data and time at which the method was assembled.
Status
The status of the method as one of the following:
ACTIVE
The method is loaded.
LOCK
The method cannot be run locally. Either the method load detected errors or the method does not run in this environment.
NOTFND
The method is not in the load table for the specified release level of the CMAS or MAS.
NOTRAN
The transaction listed in the Tran field is not defined in the CICS PCT.
TRAP1
Trap level 1 is set for this method.
TRAP1-2
Trap levels 1 and 2 are set for this method.
TRAP1-32
Trap levels 1 - 32 are set for this method.

End of change

LIST START

Lists the status of all methods you’ve started or attached. Figure 36 shows an example of the LIST START display.

Figure 36. An example LIST START display
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 Select P=Purge V=View MAL D=Dump MAL  END=Cont.
 S Type   Meth Task N Status
 _ START  XQCQ   828  Completed, RESPONSE:OK
 _ START  NSCR   844  Completed, RESPONSE:OK
 _ START  NQPG   860  Completed, RESPONSE:EXCEPTION(ABEND)

The fields on this display are:

Field
Description
Type
Either START or ATTACH, depending on which command you used to start the method.
Meth
The name of the method.
Task
The CICS task number of the method.
Status
The method’s status as one of the following:
Note:
The error "Method is no longer running!" means the status in an internal table indicates the method should be running but the CICS task has been found not active via a CICS inquiry. This error is also used for attached tasks that may have timed out trying to communicate a request back into the CMAS.

You can enter the following in the selection field:

Command
Description
P
Purges the MAL for this method.
Note:
You cannot purge a MAL unless its status is "Completed".
V
Formats the MAL.
D
Calls the CODB transaction with the address of the MAL for hexadecimal dumps.
A
Causes an ATTACH command to be created for the method with the context and scope of the original attach being viewed. The existing MAL is used as a starting point, but a new task will appear on the LIST START display.
E
Causes an EXEC command to be created for the method with the context and scope of the original attach being viewed. Executed methods do not appear in the LIST TASK display; they are called directly by COD0 and the results are displayed immediately.
S
Causes a START command to be created for the method with the context and scope of the original start being viewed. The existing MAL is used as a starting point, but a new task will appear on the LIST START display.

LIST STCB

Lists the server-client control blocks. These control blocks are used by CICSPlex SM communications and the end-user interface to request work in a CMAS. Figure 37 shows an example of the LIST STCB display.

Figure 37. An example LIST STCB display
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 V=View MAL  D=Dump MAL  S=Dump STCB  X=Dump XLSP
 S Address  Status  Last Usr From Error  CSFM Context  Scope  OutQue
 _ 060C9BA0 Avail            COM      0  TSPV PLEX2C1  PLEX2C1  NO
 _ 060C97C0 Avail            COM      0  TSCV                   NO
 _ 060C93E0 Avail            COM      0  CSAC                   NO

The fields on this display are:

Field
Description
Address
The address of the STCB control block.
DataAlet
The status of the control block as one of the following:
Avail
Available and waiting for work.
Free
Available, but not waiting for work.
In Use
A MAL is being run.
Timeout
A conversation with the STCB timed out.
Last Usr
For a TSO end-user interface request, the user ID of the TSO user.
From
Where the request for this STCB came from, as either COM, for communications, or EUI, for the TSO end-user interface.
CSFM
The ID of the method last run using this STCB.
Context
The CMAS or CICSplex involved in the last request.
Scope
The CICSplex, CICS system group, or CICS system involved in the last request.
OutQue
For a TSO end-user interface request that was routed to multiple CMASs and MASs, indicates whether the status of each was reported individually or combined into a single response.

LIST TASK

Start of changeDisplays all CICSPlex SM tasks and the methods being called within them. Figure 38 shows an example of the LIST TASK display typical of those produced under CICS/ESA, and CICS/MVS.

Figure 38. An example LIST TASK display (CICS/ESA, CICS/MVS)
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 DUMP L=Loadpt P=oPb O=Ossb S=Stack M=Mal B=modB E=moEb V=MAL END=Cont.
 S Task # METH Load-pt  oPb      Ossb     Stack    Mal      modB     moEB
 _    27  XLOP 00000000 00489FA8 00489FF0 0048A014 04283580 000CF820 00000000
 _    27  DBG1 8A5B9690 00489FA8 00489FF0 0048A118 0A4602E4 000CF820 00000000
 
 _    20  XLEV 00000000 00494FA8 00494FF0 00495014 04273580 000CF820 00000000
 
 _    23  XLOP 00000000 00491FA8 00491FF0 00492014 04277580 000CF820 00000000
 _    23  TIST 0A55C430 00491FA8 00491FF0 00492118 00490FD4 000D7D00 04274160
 _    23  XSWC 0A514018 00491FA8 00491FF0 004925A0 0049244C 000D29F4 000DE0B0
 
 _    24  XLOP 00000000 0048DFA8 0048DFF0 0048E014 0427F580 000CF820 00000000
 _    24  RSWT 0A574728 0048DFA8 0048DFF0 0048E118 0048CFD4 000DAED4 042744D0
 _    24  XSWC 0A514018 0048DFA8 0048DFF0 0048E4D8 0048E3BC 000D29F4 000DE0B0

This display shows one line per method with a space between CICSPlex SM tasks. The fields on this display are:

Heading
Description
Task #
The CICS task number.
Note:
Do not use the task number to purge the CICSPlex SM transaction, as CICSPlex SM recovery will not be entered and CICSPlex SM system control block chains will be destroyed.
METH
The name of the method running at that stack level.
Load-Pt
The address of the method’s load point.
oPb
The address of the object process block (one per CICSPlex SM CICS task) that points to all the OSSBs for this task.
Ossb
The address of the stack segment block to which this method’s stack is attached.
Stack
The address of the method’s stack.
Mal
The address of the MAL for the method.
modB
The address of the MODB for the component.
moEB
The address of the MOEB for the component.
End of change

You can enter the following in the selection field:

Command
Description
L
Calls CODB to display the load point of the method.
P
Calls CODB to display the OPB.
O
Calls CODB to display the OSSB.
S
Calls CODB to display the stack.
M
Calls CODB to display the MAL.
B
Calls CODB to display the MODB.
E
Calls CODB to display the MOEB.
V
Formats the MAL display as you would have if you entered it.
U
Allows updating of the MAL in-flight.
R
Lists the contents of all the registers (AR and GP). From this list you can enter:
D
Calls CODB to display data at that location using the AR register.
A
Calls CODB to display data at that location using only the general purpose register (ALET will be zero).
CICSPlex SM chain checking

During a LIST TASK command the entire chain of CICSPlex SM blocks that apply to a task are followed. The eyecatcher for each of the blocks is checked, in addition to the forward and backward methods within stacks and possible recursive chains. If any errors are found, you may see one of the following error messages after the last valid entry:

Stack chain broken at AAAAAAAA

This error indicates that the previous method’s ID within a stack chain does not match the previous method’s ID. This may be the case if code within the method overlays the stack header. AAAAAAAA is the address of the invalid stack frame.

OPB chain error at AAAAAAAA

Object process blocks are created for each CICS CICSPlex SM task. They are chained together for the component ID of the first method in the chain. If this chain points back to itself (a recursive chain), this message appears. AAAAAAAA is the address of the OPB that was next after the previously displayed OPB.

Eyecatcher failed for CSFM at AAAAAAAA

If an eyecatcher of a control block that is visited during a LIST TASK is incorrect, this message appears. AAAAAAAA is the address of the control block in question and CSFM is its name.

DFHEIBLK block invalid at AAAAAAAA, OPB at AAAAAAAA
invalid

The task’s object process block is really the CICS DFHEISTG area. In this area is a pointer to the task’s CICS EIB block, which is checked during LIST TASK commands.

LIST VIEWS

Lists all ISPF end-user interface views that can be captured. You can qualify the list by using the mask option to specify a generic key. Figure 39 shows an example of the LIST VIEWS display. The mask option was used to display only those views that begin with the letter A.

Figure 39. An example LIST VIEWS A* display
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 Enter END to exit.
 View      DistName Type     Class Name    Desc
 ACTNDEF   EYUZEGP0 TRTAA    ActDef        Action Definitions
 ADMANLS   EYUZEAZ4 TMENU3   ViewTable     Real Time Analysis Admin Views
 ADMCONFG  EYUZEAZ1 TMENU3   ViewTable     CMAS Configuration Admin Views
 ADMIN     EYUZE$MM TMENU2   ViewTable     ============================
 ADMMON    EYUZEAZ2 TMENU3   ViewTable     Monitor Admin Views
 ADMTOPOL  EYUZEAZ5 TMENU3   ViewTable     Topology Admin Views
 ADMWRKLD  EYUZEAZ3 TMENU3   ViewTable     Workload Manager Admin Views
 AIMODEL   EYUZEK50 TOPERATE CicsAiModel   Auto Install Models
 AIMODELS  EYUZEK5S TOPERATE CicsAiModel   Auto Install Model Summary
 ANALYSIS  EYUZEAZR TMENU1   ViewTable     Real Time Analysis Views

The fields on this display are:

Field
Description
View
The name of the view.
DistName
The name of the source member for the view.
Type
The type of view, which determines what selection list the view appears on.
Class Name
An internal description of the view.
Desc
The description of the view as it appears on the end-user interface.

POST (posting an ECB)

The POST command posts an ECB using the MVS POST command.

The format of the POST command is:

POST address

where address is a 1- to 8-character hexadecimal number that is the address at which the ECB resides.

No check is made to see whether an ECB exists at this address or whether it is already posted; an MVS POST command is simply issued.

Note:
You can use the DUMP command or the CODB transaction to find the address.

PRINT (printing data areas under CICS/ESA, CICS TS)

The PRINT command prints a CICSPlex SM data area. PRINT uses the CICS spool facility to write the data area as an output file called Sxxxxxxx, where xxxxxxx is a numeric identifier.

The format of the PRINT command is:

PRINT [parameters...]

where the parameters are:

/resname
Prints the specified allocated resource.
alet addr size
Prints an EPTR at the specified address for the specified number of bytes.
CLIST token
Prints the cache list of the specified token, where token is an 8-byte token entered as two 8-character hexadecimal fields.
EIB compid
Prints the EIB for the specified component.
EIS compid
Prints the EIS for the specified component.
hexaddr size
Prints memory at the specified address for the specified number of bytes.
MAL addr
Formats and prints the MAL at the specified address.
method
Prints the code for the specified method.
MODB compid
Prints the MODB for the specified component.
MODD
Prints the MODD.
MOEB compid
Prints the MOEB for the specified component.
OPB compid
Prints the object process block for the specified component.
QUE token
Prints the queue of the specified token, where token is an 8-byte token entered as two 8-character hexadecimal fields.
STAKEND compid
Prints the current stack for the specified component.
STAKSTRT compid
Prints the first stack for the specified component.
XLWA
Prints the XLWA.

PURGE (purging an allocated resource)

The PURGE command purges an allocated resource.

The format of the PURGE command is:

PURGE /resname

where:

/resname
Is the name of the resource you allocated. The storage assigned to the resource is removed from the system.
Note:
You can also purge allocated storage using the P command from the LIST ALLOC display.

START (starting a method in the CMAS)

Start of changeThe START command starts a method running within the CMAS. End of change

The format of the START command is:

START method [termid]

where:

method
Is the name of a CICSPlex SM method.
termid
Is a terminal ID.

The message argument list (MAL) of the method is displayed. For details about how to enter data from this display, see Displaying a MAL from COD0. For a list of valid responses to this command, see Running a method.

Figure 40 shows an example of the START display.

Figure 40. An example START display
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 Overtype fields and press ENTER to edit, END to proceed, CANCEL to abort.    Dn
 IN
     ENM FUNCTION( SETCRGN )
     CHR DEBUG(          )
     BIN SYSTEM_AKP(          )
     BIN SYSTEM_AMAXTASKS(          )
     BIN SYSTEM_CUSHION(          )
     CHR SYSTEM_DTRPROGRAM(          )
     BIN SYSTEM_ECUSHION(          )
     BIN SYSTEM_MAXTASKS(          )
     BIN SYSTEM_MROBATCH(          )
     BIN SYSTEM_PRTYAGING(          )
     BIN SYSTEM_RUNAWAY(          )
     BIN SYSTEM_SCANDELAY(          )
     BIN SYSTEM_SYSDUMP(          )
     BIN SYSTEM_TIME(          )
     BIN TRACEDEST_AUXSTATUS(          )
     BIN TRACEDEST_GTFSTATUS(          )
     BIN TRACEDEST_INTSTATUS(          )
     BIN TRACEDEST_SWITCHSTAT(          )
     BIN TRACEDEST_SWITCHACT(          )

The START command starts a CICS task that eventually executes method DBG2. This method is created dynamically by COD0 in every component.

TRACE (setting CICS and CICSPlex SM trace flags)

The TRACE command can be used to:

The format of the TRACE command is:

TRACE [parameters...]

where the parameters are :

ON [RESET|START]
OFF [RESET|STOP]
USER [RESET]
Controls the settings of the CICS component trace flags.
ON
Turns all CICS component flags on, which produces slightly more output than the normal CICS trace settings.
OFF
Turns all CICS component trace flags off, which results in almost no output at all (some CICS components do not have trace flags).
USER
Start of changeTraces only the CICS component application domains (AP0000 through APFFFF).End of change
RESET
Causes tracing to start at the beginning of the auxiliary trace data set, overwriting any existing output.
START
Opens the auxiliary trace dataset.
STOP
Closes the auxiliary trace dataset.
FLAG
Shows the trace flags of each CICSPlex SM component. You can change the trace flag settings of one or more CICSPlex SM components by overtyping the component's bit setting.
SWITCH
Start of changeSwitches the CICS auxiliary trace data sets and reports on which is active.End of change

Changes made to CICS and CICSPlex SM trace settings from the COD0 debugging transaction remain in effect after you exit the transaction.

TRACK (setting trace flags by calling structure)

The TRACK command sets CICSPlex SM trace flags based on the calling structure.

The format of the TRACK command is:

TRACK target relation calling flags id

where the parameters are:

target
The name of the method to be traced. You can provide a generic method name by specifying an asterisk (*) at the end of the name or in place of the name (to indicate all methods).
relation
The relationship to the calling method as one of the following:
FROM
Sets the trace for the target only when the direct caller is the calling method.
STAK
Sets the trace for the target only if the calling method is somewhere in the CICSPlex SM stack.
calling
The name of the method that calls the target method either directly or indirectly. You can provide a generic method name by specifying an asterisk (*) at the end of the name or in place of the name (to indicate all methods).
flags
The trace flags to be set. The trace flags are set according to group names and are dependent on the underlying trace facility. The trace flags will be provided by IBM® support should you need to use this facility.
id
An optional user or task ID:
Uxxxxxxxx
where xxxxxxxx is a 1-to 8-character EUI user ID.
Tnnnnnnn
where nnnnnnn is a 1- to 7-position CICS task number that can be obtained by issuing either the LIST TASK or CEMT INQ TASK command.

For example:

  TRACK XD* STAK CI* SPEC UTOM

activates all trace flags for any data repository method that is called directly or indirectly from any communication initialization method, when the task is handling an EUI request from ID TOM.

TRAP (setting trace flags for a method)

The TRAP command sets trace flags on for a specific CICSPlex SM method.

The format of the TRAP command is:

TRAP method [1|2|ALL|OFF]

where:

method
Is the name of a CICSPlex SM method.
1|2|ALL|OFF
Sets the trace flags for the specified method:
1
Sets level 1 trace flags on.
2
Sets level 1 and level 2 trace flags on.
ALL
Sets level 1-32 trace flags on.
OFF
Sets tracing for the method back to the flags specified on the COD0 TRACE command, the EYUPARMS start-up parameters, or the CMAS or MAS view command.

Displaying a MAL from COD0

When entering into a MAL formatted by the COD0 debugging transaction, all input is validated for both physical and logical properties.

Format of the MAL display

When viewing or updating a MAL, either from a START, ATTACH, or EXEC command, or from LIST output, the format of the display is as shown in Figure 41.

Figure 41. Sample formatted MAL display
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 Fields with "->" required.
 IN
    *ENM FUNCTION( TEST )
     CHR DEBUG(          )
 ->  FLG FLAG_VALUES(              )
 OUT
    *ENM RESPONSE(                 )
    *ENM REASON(                 )

As shown in Figure 41, IN and OUT eyecatchers separate the major sections of the MAL. Each field name in the IN and OUT sections can be preceded by three other indicators:

Note:
The FUNCTION field is completed by the COD0 debugging transaction and cannot be changed.

Field types

The three-character code that precedes a field determines what can be entered in the field and the kind of data that is displayed. Table 5 shows the input allowed for each field type.

Table 5. Field types
Type Format Input allowed
BIN BIN(n) Hexadecimal number
BLK BLOCK Hexadecimal number for address or decimal number for length
BUF BUFFER Hexadecimal number for address, decimal number for length, or resource name (/resname)
CHR CHAR(n) Any character
CMP COMPID Component ID or '?' for a list
DEC DEC(n) Decimal number
EBK EBLOCK Hexadecimal number for ALET and OFFSET, decimal number for length, or resource name (/resname)
ENM (names) Names defined in format or '?' for list
EPT EPTR Hexadecimal number for ALET and OFFSET or resource name (/resname)
ETK ETOKEN Hexadecimal number or resource name (/resname)
FLG FLAG Hexadecimal representation of a flag or '?' for a list
LST LIST Hexadecimal number for address, decimal number for length, or resource name (/resname)
MPL MAL Hexadecimal number or resource name (/resname)
PTR PTR Hexadecimal number or resource name (/resname)
RES RESTYPE Resource name (/resname) or '?' for a list
SDT SDT TRUE or FALSE
STR STRING(n) Any character
TIM TIMESTAMP Hexadecimal number
TKN TOKEN Hexadecimal number or resource name (/resname)

Field edits and display formats

In a MAL display, input is edited and output is formatted according to the following rules:

Field type
Format
Hexadecimal
Hexadecimal characters 0-9 and A-F, in either upper or lower case. In output, the number is right-justified and padded with zeroes.

You can enter decimal characters instead of hexadecimal by preceding the value with a backslash, as in \1234. The decimal number is internally converted to hexadecimal.

Decimal
Numeric characters 0-9, without any sign. In output, the number is right-justified and padded with zeroes.

You can enter hexadecimal characters instead of decimal by preceding the value with a backslash, as in \ABCD. The hexadecimal number is internally converted to decimal.

ENM, CMP, or RES
One of the values shown in the message format. For example, if the format indicates MY_FIELD IS (A,B,C,D), you can enter A, B, C, or D. You can also enter a question mark (?) to display a list of possible values; you can select one to be copied into the MAL.

For a field type of RES, you can use the HELP command to display a list of known resource types, such as HELP RESOP or HELP CVDA.

Flags
A hexadecimal value representing a flag name, including a combination of flag names that have been logically ORed. You can also enter a question mark (?) to display a list of possible values. You can select as many as apply; they are logically ORed and copied into the MAL.

Subfields

Many fields in a MAL consist of multiple subfields, which are divided into multiple input fields and validated separately. Each field is preceded by the suffix of the subfield. For example, the EPT field is made up of the ALET and OFFSET subfields, and looks like this when the MAL is displayed:

EPT YOUR_MAL_FIELD_NAME(A= alet O= offset)

The subfields associated with each field type are as follows:

Field type
Subfields
EPT
A=alet, O=offset
BUF
A=address, L=length, M=maximum length
BLK
A=address, L=length
EBK
A=alet, O=offset, L=length
LST
A=address, N=number

Using allocated resources

You can use the names of allocated resources (such as cache lists, data queues, data space storage, or CICS storage) in the input fields of a MAL. (For information on allocating resources, see ALLOC (allocating a resource).)

If the field contains subfields, as described in Subfields, you need enter only the resource name in the first field; the COD0 debugging transaction determines the other field types and fills them in for you.

For example, you could use the ALLOC command to allocate 4K of data space storage to the resource called /workara, as shown in Figure 42.

Figure 42. Using ALLOC to allocate a resource
 COD0 CICSPlex/SM Debugger
 CMD=> ALLOC /workara EPTR 4096                                   Scroll=> PAGE
 
 IN
 

Figure 43 shows the allocated resource, /workara, being used as input to a MAL.

Figure 43. Using an allocated resource in a MAL
 COD0 CICSPlex/SM Debugger
 CMD=>                                                            Scroll=> PAGE
 
 IN
    *ENM FUNCTION( TEST )
     CHR DEBUG(          )
     EPT OUT_ADDR(A= /workara   O=         )
 

The COD0 debugging transaction places the ALET of the allocated storage area into the A= field; the offset is automatically entered in the O= field.

Running a method

From a formatted MAL display you can enter the following commands:

CANCEL
Returns control to the previous display without processing the MAL.
DUMP mal-field
Determines the type of the specified field and creates an appropriate DUMP command to call the CODB debugging transaction. mal_field can be any field on the formatted MAL display.
END
Edits the MAL and then either ATTACHes, EXECutes, or STARTs the method. Control returns to the previous display.

If you return to the COD0 main menu while a method is running, a LIST START command is automatically issued.

FLAG mal-field
Displays a list of the specified field’s bit values (that is, their names from the Message Argument Format). Those that are currently set are prefixed by a plus sign (+). mal-field can be any field on the formatted MAL display that has a type of FLG. If the name you enter is neither part of the MAL nor an FLG field, an error message is issued.
GO
Edits the MAL and then either ATTACHes, EXECutes, or STARTs the method. Control remains at the formatted MAL display. You can enter the same or different data, and issue GO or END again.

You can use the LIST or LIST START command to check the progress of the started or attached method. When you END the LIST display control returns to the formatted MAL display.

NEXT
For the results of an ATTACHed method that either ran in multiple MASs or ran multiple times in a CMAS, displays the MAL that ran next.
PREV
For the results of an ATTACHed method that either ran in multiple MASs or ran multiple times in a CMAS, displays the MAL that ran previously.

Notes:
  1. If you press Enter without issuing a command, the MAL is edited, but not run.
  2. For the DUMP and FLAG commands, only fields that appear in the current formatted MAL display can be used as parameters. If you want to name the field of another MAL, you must first display that MAL from the LIST START or LIST TASK screen.
[[ Contents Previous Page | Next Page Index ]]