Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

UTM Diagarea

&pagelevel(5)&pagelevel

The UTM Diagarea is a process-specific trace area in which all events are logged. This area thus contains all the events that occurred immediately before a service or application aborted.

The UTM Diagarea is written cyclically. Two cycles are separated by a dividing line comprising '=' characters and blanks. The newest entry is above the dividing line and the oldest entry is below the dividing line. Every entry is 136 or 256 (64-bit) bytes in length. The total number of entries that can be accommodated by the UTM Diagarea depends on the UTM generation parameter MAX TRACEREC.

The following types of entries are written to the UTM Diagarea:

  • UTM records (type KDCS)

    UTM records of type KDCS are written when the following events occur:

    • a KDCS call in a program unit or

    • an internal call to the UTM system code or

    • a call to the administration programming interface or

    • an internal PEND ER call by openUTM (system PEND ER) in response to a serious error.

Additional trace information is written for calls from the administration interface (KDCS-opcode=ADMI), see section “Administration DIAGAREA”.

If a PEND ER is issued by the system, then the entry in bytes 22- 57 contains an error text.

  • UTM records when starting and terminating user-specific event exits:

    • INPUT exit program (types INXS and INXE)

    • START exit program (types STXS and STXE)

    • VORGANG exit program (types VGXS and VGXE)

    • HTTP exit program (types HTXS and HTXE)

  • UTM records to identify the service (type VGID)

    A VGID record is written to the UTM Diagarea every time a program unit is started and when a PGWT call returns.


  • UTM records when HTTP functions are called (type HTTP )
    A HTTP record is written when a HTTP function is called.

Header for the records in the UTM Diagarea

Every record starts with a header containing the following information:

Byte

Meaning

dec.hexadec.

0-1

00-01

Count of the current entries in the DIAGAREAs (UTM and DB)

2-5

02-05

Type identifications (KDCS, VGID, INXS, INXE, STXS, STXE, VGXS, VGXE, ITRC, HTXS , HTXE, HTTP)

6-7

06-07

Currently not used (preset to ’= =’)

8-15

08-0F

Time stamp

Structure of the header


As of byte 16, the content of the records depends on the record type.

Structure of the UTM Diagarea for a KDCS call from a program unit

Byte

Field name and meaning

dec.                

hexadec.

16-19

10-13

KCOP:1

user operation code: INIT, MGET, MPUT, etc.

internal operation code: see "table KCOP"

20-21

14-15

KCOM: operation modification

22-23

16-17

KCLA: area length or queue level (in the case of QCRE) or
KCLKBPRG: length of KB program area with INIT

24-25

18-19

KCLM: message length or
KCLPAB: length of standard primary work area with INIT
KCWTIME: wait time in seconds in the case of DGET

26-33

1A-21

KCRN: reference name




MCOM call

34-41

22-29

KCMF:name of the abstract syntax
KCLT: LTERM name of the LTERM partner or
KCUS: user ID or
KCPA: name of the partner application (with APRO call)

KCPOS:
destination
of positive
confirmation
job

42-43

2A-2B

KCDF: screen function, see "table KCDF"

KCNEG:
Destination
of negative
confirmation
job



DPUT/DADM

DGET

QCRE

PADM

APRO

44

2C

KCMOD: mode
(“A”/”R”/”_”)

KCQTYP:
destination type
("U"/"Q"/"T")

KCQMODE:
mode ("S"/ "W"/bin.
zero)

KCACT: action

(ON/OFF/CON/DIS)

KCPI:
service ID

45-47

2D-2F

KCTAG: days



empty



empty

48-49

30-31

KCSTD: hours

KCADRLT:
new LTERM
name of the printer

50-51

32-33

KCMIN: minutes

KCCOMID:
complex ID

52-53

34-35

KCSEC: seconds

KCOF:
OSI TP functions

54

36

KCQTYP:
destination type
("U"/"Q"/bin. zero)

55-57

37-39

empty

empty

58-89

3A-59

KCRFELD in KCKBC: KB return information area see "table KCRFELD"

92-95
(32-Bit)
96-103 
(64-Bit)2

5C-5F
(32-Bit)
60-67
(64-Bit)2

Return address to the program unit (the address points to a position after the KDCS call in the program unit)

96-99
(32-Bit)
104-111
(64-Bit) 2

60-63
(32-Bit)
68-6F
(64-Bit) 2

Address of the user data area (2nd parameter of the KDCS call)

100-103
(32-Bit)
112-119
(64-Bit) 2

64-67
(32-Bit)
70-77
(64-Bit) 2

Service index

104-111
(32-Bit)
120-127
(64-Bit) 2

68-6F
(32-Bit)
80-87
(64-Bit) 2

KCLOGTER in KCKBC: LTERM name

112-119
(32-Bit)
128-135
(64-Bit) 2

70-77
(32-Bit)
88-8F
(64-Bit) 2

KCBENID in KCKBC: name of the current user ID

Structure of an entry of the UTM Diagarea for a KDCS call


1If KCOP=INFO (bytes 16-19) and in the event of operation modification KCOM=CK (bytes 20-21), the message area of the logged call is written to the next entry of the UTM Diagarea at a length KCPAC. This information is of interest for diagnostic purposes, as it logs the call to be checked. 

2 The 64 bit specifications only apply to Unix, Linux and Windows systems.

For internal calls from openUTM, the following codes are entered in the KCOP field:

KCOP contents

Situation in which this entry was written

Entries in subsequent fields

STRT

Start of UTM application program, beginning of start handling in the UTM system code

No entry

WAIT

UTM process is waiting in the system code for the next request

No entry

CONT

Continuation in UTM system code after a DB action via KDCROOT or after the INPUT exit is called

KCRCCC, KCRCKZ and KCRCDC only. for INPUT exit:
parameters, see table "UTM Diagarea after a call of the INPUT exit"

NOOP

Buffer area of MESSAREA must be emptied (only possible when event monitor is switched on)

- - -

ADMI

UTM administration action

UTM internal interface


Structure of KCRFELD

Byte

Field name and meaning

dec.hexadec.

58-59

3A-3B

KCRDF: screen function return
KCRWVG: number of waiting services with DGET

60-61

3C-3D

KCRLM: actual length of the message



INFO CK call

MGET call

SIGN ON call

62

3E

KCRINFCC:
KDCS return code
of the KDCS
call checked

KCVGST:
service status

KCRSIGN1:
primary code

63

3F

KCTAST:
transaction status

KCRSIGN2:
secondary code

64

40

empty

65

41

empty

KCRMGT: message type


66-68

42-44

KCRCCC: KCDS return code

69

45

KCRCKZ: identifier: P (productive or live operation application),

70-73

46-49

KCRCDC: internal return code

74-81

4A-51

KCRMF: return of the format identifier or the abstract syntax

82-89

52-59

KCRPI: service identification return
KCRUS: user ID in the case of SIGN ST or creator of the message with DGET
KCRQN: name assigned by openUTM to the temporary queue in the case of QCRE NN

UTM Diagarea after a call of the INPUT exit

After the INPUT exit is called, openUTM enters the most important parameters that the exit receives or sets (KCPAC) in the KDCS record:

Byte

Field name and meaning

dec.hexadec.

16-19

10-13

KCOP: "CONT" is entered here

20-25

14-19

empty

26-33

1A-21

KCIFCH: first 8 characters of input

34-35

22-23

KCICVST: service status: "ES"/"ET"/"RS"/"EC

36-37

24-25

KCIFKEY: value of F key: 1,...,24

38-39

26-27

KCIKKEY: value of K key: 1,...,14

40-41

28-29

KCICFINF: information about control fields: "UN"/"NO"/"ON"/"MO"

42-49

2A-31

KCINTAC/KCINCMD: next TAC to be started or next user command

50-51

32-33

KCICCD: code for effect of input: "ER"/"CC"/"SC"/"ST"/"CD"

52

34

KCICUT: truncate TAC: "Y"/"N"

53

35

---

54-57

36-39

KCIERRCD: error info for data display terminal

58-...

3A-...

the following is not relevant for diagnostics

Structure of an UTM Diagarea entry after a call of the INPUT exit


Error texts in UTM Diagarea after SYSTEM PEND ER

To allow more rapid diagnosis in the event of a SYSTEM-PEND ER, the corresponding line of the UTM Diagarea contains a printable error text in bytes 22-57.

The following table contains a list of all error texts, plus the relevant cause of the error, the module where the PEND ER occurred and the type of error involved (system error or user error).

The error texts marked with *) appear only on BS2000 systems and the values marked with **) appear only on Unix, Linux and Windows systems.

Error text

Cause, module

Error type

APPL. PROGRAM DOES NOT EXIST

No indicator  for a program unit existed when program unit started (70Z with KR01).

System error

APPL. PROGRAM WITHOUT PEND

Application program was not terminated with PEND. (84Z)

User error

ASYNC. PROGRAM NOT FOUND

Asynchronous program no longer available (program may have been exchanged). PEND ER dump follows with 70Z and KR02.

User error

ERROR IN "START-TP" OF LGCON

The language connection module supplied an incorrect return code when program unit was started.

System error

KB END LABEL OVERWRITTEN
                                                                                                                                             

The KB in the application program is greater than specified in the UTM generation (70Z with KR04).
Action: change KB= operand in the MAX statement  

User error

SPAB END LABEL OVERWRITTEN

The SPAB in the application program is greater than specified in UTM generation (70Z with KR05).
Action: change SPAB= operand in MAX statement

User error

KCRCCC >= 70Z AFTER UTM SVC

UTM SVC set KCRCCC in KB header to >= 70Z

User/system error

ROOTDATA CODE INVALID **)


UTM SVC set ROOTDATA CODE to an invalid value

System error

ERROR ROUTINE XT... ENTERED **)

A signal with the number ...(in KDCRTDI) occurred.

User/system error

ERROR ROUTINE EXIT ENTERED **)

An illegal exit() call (COBOL: STOP RUN statement) was recognized while a program unit was running; see also under return code KCRCDC= EXIT.

User error

ERR IN STXIT-ROUTINE OF LGCON *)

During STXIT handling, an faulty return code was supplied by the Language Connection Module.

User/system
error

STXIT WITH XT.. ENTERED *)

A STXIT with weight .. occurred.

System error

DB ERRORCODE = TA_CHAIN_RSET

The database connection module supplied return code' TA_CHAIN_RSET' .
If this return code was issued by one of the messages K210, K211 or K216 with XAER_DUPID, the cause could be that the previous application run was terminated abnormally, and left a transaction in the database and that a new KDCFILE was generated in this state.
Action in this event: shut down and restart the database.

System error

KDCS CALL IN VORGANG EXIT

An illegal KDCS call was made in the VORGANG exit program.

User error

VORGANGEXIT PROGRAM  NOT LOADED

The VORGANG exit program is not loaded.

User error

KDCS CALL IN FORMAT EXIT *)

An illegal KDCS call was made in the FORMAT EXIT program.

User error

DATABASE DOWN AT USER DB CALL

The database was no longer connected at the time of the CALL to the database from the application program unit.

User/
system error

ILLEGAL RTCODE FROM DBCON

The database connection module supplied an illegal error code.

System error

NO DB CALL ALLOWED IN SIGN-ON

The sign-on service has issued an illegal DB-USER-CALL

User error

PROGRAM INDEX = 0 INVALID **)

UTM SVC set an invalid program index.

System error

DYNAM. PROGRAM LOADING FAILED *)

An error occurred when loading a program.
PEND ER dump with 70Z and KR09

User/system
error

Error texts in UTM Diagarea after SYSTEM PEND ER


Service identification entry (type VGID)

Byte 32-Bit

Byte: 64-Bit **)

Meaning

dec.

hexadec.

dec.

hexadec.

16

10

16

10

Service ID

17

11

17

11

Session counter

18-19

12-13

18-19

12-13

Transaction counter in the service

20-23

14-17

24-31

18-1F

Service counter

24-27

18-1B

32-39

20-27

Sum of USED and ERROR for the current TAC

28-31

1C-1F

40-47

28-2F

Length of the global transaction identifier (GTRID) of the XID

32-35

20-23

48-55

30-37

Length of the branch qualifier (BQUAL) of the XID

36-115

24-73

56-137

38-89

The first 80 bytes of the XID data *)

116-117

74-75

138-139

8A-8B

Index to the program table

118-119

76-77

140-141

8C-8D

Index of the service exit in the program table

120-127

78-7F

142-149

8E-95

Name of the transaction code that started the service

128-135

80-87

150-157

96-9D

Name of the current transaction code

Structure of the service identification entry

*) For details on XID, GRTID and BQUAL, please refer to the corresponding XA specification
**) only valid for Unix, Linux and Windows systems

VORGANG exit entry (types VGXS and VGXE)

Byte 32-Bit

Byte: 64-Bit **)

Meaning

dec.

hexadec.

dec.

hexadec.

16

10

16

10

Service ID

17

11

17

11

Session counter

18-19

12-13

18-19

12-13

Transaction counter in the service

20-23

14-17

24-31

18-1F

Service counter

24-27

18-1B

32-39

20-27

Sum of USED and ERROR for the current TAC

28-31

1C-1F

40-47

28-2F

Length of the global transaction identifier (GTRID) of the XID

32-35

20-23

48-55

30-37

Length of the branch qualifier (BQUAL) of the XID

36-115

24-73

56-137

38-89

The first 80 bytes of the XID data *)

116-117

74-75

138-139

8A-8B

Index to the program table

118-119

76-77

140-141

8C-8D

Index of the service exit in the program table

120-127

78-7F

142-149

8E-95

Name of the transaction code that started the service

128-135

80-87

150-157

96-9D

Name of the SERVICE exit program

Structure of the SERVICE exit entry

*) For details on XID, GRTID and BQUAL, please refer to the corresponding XA specification
**) only valid for Unix, Linux and Windows systems



INPUT exit entry (types INXS and INXE)

Byte

Meaning

dec.

hexadec.

16-31

10-1F

String INPUT-EXIT-FORM or INPUT-EXIT-USER or INPUT-EXIT-LINE

32-39

20-27

Program name of the INPUT exit

40-47

28-2F

The first 8 characters of the input message

48-55

30-37

Format name (empty)

56-63

38-3F

TAC name

64-65

40-41

Status

66-67

42-43

F key

68-69

44-45

K key (empty)

70-71

46-47

Control field

72-79

48-4F

Lterm name

80-87

50-57

User name

88-119

58-77

(Not used)

120-127

78-7F

Next TAC or command

128-129

80-81

Continuation code

130

82

CUT TAC

131

83

(Not used)

132-135

84-87

Error code

Structure of the INPUT exit entry


START exit entry (types STXS and STXE)

Byte

Meaning

dec.

hexadec.

16-31

10-1F

String START-EXIT-#
(# = 1 - 8 stands for the number of the START exit.)

32-39

20-27

Program name of the START exit

40-47

28-2F

String STARTUP (fixed name of the TAC)

48-63

30-3F

Indicator, if the first process or the follow-up process is the string

Structure of the START exit entry


HTTP exit entry (Typ HTXS und HTXE)

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
16101610Opcode: HTTP_GET_EXIT = 1, HTTP_PUT_EXIT = 2
17111711Returncode: OK = 0; ROOT_INT_PEND_ER = 1
 18 12 18 12Returncode of the HTTP exit
 19 13 19 13InOut indicator: I/O
 20-23 14-17 24-31 18-1FPointer to KDCS parameter area
 24-27 18-1B 32-35 20-23KDCS operation code
 28-29 1C-1D 36-37 24-25Counter for successfully read MGET message parts
 30-31 1E-1F 36-39 26-27Length of remaining message part (nach RCCC=02Z)
 32-33 20-21 40-41 28-29Index of HTTP exit program
 34-35 22-23 42-43 2A-2B
 36-51 24-33 44-59 2C-3BHTTP info structure (see INIT PU)
 52-55 34-37 64-71 40-47Pointer to MGET structure information
 56-59 38-3B 72-79 48-4FNumber of message parts from the MGET structure information
 60-63 3C-3F 80-87 50-57Pointer to current message part

Structure of  the HTTP exit entry

**) only valid for Unix, Linux and Windows systems


HTTP function entry (Typ HTTP)

The structure of the HTTP record depends on the called function. Each record starts with the following structure.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
16-4710-2F16-4710-2F Alphanumeric name of the HTTP function, e.g. kcHttpGetHeaderByName
48-9530-5F48-9530-5FAlphanumeric return code of the HTTP function, e.g. KC_HTTP_OK (0)
96-9960-6396-9960-63Sedecimal return code of the HTTP function

**) only valid for Unix, Linux and Windows systems


The HTTP record of function kcHttpGetHeaderCount contains the following additional information.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
100-10364-67104-11168-6F Number of HTTP header fields of the HTTP request

**) only valid for Unix, Linux and Windows systems


The HTTP record of function kcHttpGetHeaderByIndex contains the following additional information.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
100-10364-67104-11168-6F Number of HTTP header fields of the HTTP request
104-107 68-6B112-11970-77Index of the requested HTTP header field
108-111 6C-6F120-12778-7FAddress of the buffer for the name of the HTTP header
112-11570-73128-13580-87Length of the buffer for the name of the HTTP header
116-11974-77136-14388-8FLength of the name of the HTTP header
120-12378-7B144-15190-97Address of the buffer for the value of the HTTP header
124-1277C-7F152-15998-9FLength of the buffer for the the value of the HTTP header
128-13180-83160-167A0-A7Length of the value of the HTTP header

**) only valid for Unix, Linux and Windows systems


The HTTP record of function kcHttpGetHeaderByName contains the following additional information.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
100-10364-67104-11168-6F Address of the name of the HTTP header
104-10768-6B112-11970-77Length of the name of the HTTP header
108-1116C-6F120-12778-7FAddress of the buffer for the value of the HTTP header
112-11570-73128-13580-87 Length of the buffer for the value of the HTTP header
116-11974-77136-14388-8F Length  of the value of the HTTP header

**) only valid for Unix, Linux and Windows systems


The HTTP record of functions kcHttpGetMethod, kcHttpGetPath, kcHttpGetScheme, kcHttpGetVersion, and kcHttpGetQuery contain the following additional information.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
100-10364-67104-11168-6F Address of the buffer for the return value of the fu nction
104-10768-6B112-11970-77 Length of the buffer for the return value of the function
108-1116C-6F120-12778-7F Length of the return value of the function , e.g. of the HTTP path

**) only valid for Unix, Linux and Windows systems


The HTTP record of function kcHttpGetMsg contains the following additional information.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
100-10364-67104-11168-6F Addresse of the address of the HTTP message body
104-10768-6B112-11970-77 Address of the HTTP message body
108-1116C-6F120-12778-7F Length of the HTTP message body

**) only valid for Unix, Linux and Windows systems


The HTTP record of function kcHttpPutHeader contains the following additional information.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dez.hexadez.dez.hexadez.
100-10364-67104-11168-6F Address of the name of the HTTP header
104-10768-6B112-11970-77 Address of the value of the HTTP header
108-1216C-79120-12778-7FFirst 14 characters of the name of the HTTP header
122-1357A-87128-13580-87First 14 characters of the value of the HTTP header

**) only valid for Unix, Linux and Windows systems


Der HTTP-Record der Funktion kcHttpPutStatus contains the following additional information.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
100-10364-67104-11168-6F status code
104-10768-6B112-11970-77 Address of the reason phrase
108-1356C-87120-14778-93 First 28 characters of the reason phrase

**) only valid for Unix, Linux and Windows systems


The HTTP record of function kcHttpPutMsg contains the following additional information.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
100-10364-67104-11168-6F Address of the given message fragment
104-107 68-6B112-11970-77Length of the given message fragment
108-111 6C-6F120-12778-7FAddress of the address for the accumulated HTTP message body
112-11570-73128-13580-87Address for the length of the accumulated HTTP message body
116-11974-77136-14388-8FAddress of the accumulated HTTP message body
120-12378-7B144-15190-97Length of the accumulated HTTP message body
124-1277C-7F152-15998-9FSize of the buffer for the accumulated HTTP message body

**) only valid for Unix, Linux and Windows systems


The HTTP record of function kcHttpPercentDecode contains the following additional information.

Byte 32-Bit

Byte 64-Bit **)

Meaning

dec.hexadec.dec.hexadec.
100-10364-67104-11168-6F Requested type of normalization
104-107 68-6B112-11970-77 Address of the message to be normalized
108-111 6C-6F120-12378-7BLength of the message to be normalized
112-11570-73124-1317C-83Address for the length of the normalized message
116-11974-77132-13584-87Length of the normalized message
120-12278-7A136-13988-8Bin case of error: erroneous characters

**) only valid for Unix, Linux and Windows systems


Example

In the first two examples, the hexadecimal part of the DUMP entry was omitted. The fourth example shows how the hexadecimal part is used in evaluating C names and length fields (KCLM, KCLA, etc.).

  1. Incorrect operation code in a KDCS call:

      KDCROOT : UTM Diagarea
       .
       .
       0012 08227F2C 0000      ...           ..INIT..........................
            08227F4C 0020      ...           ............  ..    000P0000
       0013 08227F90 0000      ...           ..MPUTNT....        *f0114  ....
            08227FB0 0020      ...           ............  ..    000P0000
       0014 08227FF4 0000      ...           ..SIGNOB........................
            08228014 0020      ...           ............  ..    000P0000
       0015 08228058 0000      ...           ..XXXXFI....        ............
            08228078 0020      ...           ............  ..    79ZP0000
       0016 082280BC 0000      ...           ..PENDER:   KCRCCC >= 70Z AFTER
            082280DC 0020      ...           UTM SVC  !!

  2. A PEND ER via signal 11 is triggered by an address error:

        KDCROOT : UTM Diagarea
       0004 082279B4 0000      ...           ..INIT..t.*.....................
            082279D4 0020      ...           ............  ..    000P0000
            082279F4 0040      ...                       .....J".............
       0005 08227A18 0000      ...           ..PENDER: ERROR ROUTINE XT11 ENT
            08227A38 0020      ...           ERED     !!
            08227A58 0040      ...                       ........POOLT001....

  3. Evaluation of length fields in the dump

    For the entries in length fields you must take account of the machine-dependent type of representation (little endian or big endian)). With little endian machines, the octet with the lowest address is also the least significant octet; with big endian machines, the octet with the lowest address is the most significant octet.

    The different structures are illustrated in the following table.

    Decimal

    Hexadecimal
    INTEL processor (little
    endian)

    Hexadecimal
    RISC processor (big endian)

    228

    E400

    00E4

    In decimal fields (underscored in this example), the bytes are shown in reverse sequence.

    INTEL processor (e.g. Linux and Windows systems)

     0008   B66EC3CC 0000   07004B44 43533D3D FF86AC45 53A20D00   ..KDCS==...ES...
            B66EC3DC 0010   494E4954 00000000 00000000 00000000   INIT............
            B66EC3EC 0020   00000000 00000000 00000000 00000000   ................
            B66EC3FC 0030   00000000 00000000 00002020 00002020   ..........  ..
            B66EC40C 0040   20203030 30503030 30302020 20202020     000P0000
            B66EC41C 0050   20202020 20202020 20203D3D 00000000             ==....
            B66EC42C 0060   0A3C49B7 02000000 4C545030 30303031   .<I.....LTP00001
     0009   B66EC454 0000   08004B44 43533D3D FF86AC45 67A20D00   ..KDCS==...Eg...
            B66EC464 0010   4D474554 00006D01 00000000 00000000   MGET..m.........1
            B66EC474 0020   00002020 20202020 20200000 00000000   ..        ......
            B66EC484 0030   00000000 00000000 00000000 08004F43   ..............OC
            B66EC494 0040   204D3030 30503030 30302020 20202020    M000P0000
            B66EC4A4 0050   20202020 20202020 20203D3D 00000000             ==....
            B66EC4B4 0060   710756B7 02000000 4C545030 30303031   q.V.....LTP00001

    1When the MGET call was issued, KCLA = 365 (hexadecimal: 016D) was entered.

    RISC processor (e.g. Solaris, HP-UX, and AIX systems)

     0008   0004B2EC 0000   00074B44 43533D3D 45AC8284 000B2204   ..KDCS==E.....".
            0004B2FC 0010   494E4954 00000000 00000000 00000000   INIT............
            0004B30C 0020   00000000 00000000 00000000 00000000   ................
            0004B31C 0030   00000000 00000000 00002020 00002020   ..........  ..
            0004B32C 0040   20203030 30503030 30302020 20202020     000P0000
            0004B33C 0050   20202020 20202020 20203D3D 00000000             ==....
            0004B34C 0060   FFF25214 00000002 4C545030 30303031   ..R.....LTP00001
     0009   0004B374 0000   00084B44 43533D3D 45AC8284 000B2230   ..KDCS==E....."0
            0004B384 0010   4D474554 0000016D 00000000 00000000   MGET...m........1
            0004B394 0020   00002020 20202020 20200000 00000000   ..        ......
            0004B3A4 0030   00000000 00000000 00000000 00084F43   ..............OC
            0004B3B4 0040   204D3030 30503030 30302020 20202020    M000P0000
            0004B3C4 0050   20202020 20202020 20203D3D 00000000             ==....
            0004B3D4 0060   FF1E1315 00000002 4C545030 30303031   ........LTP00001

    1When the MGET call was issued, KCLA = 365 (hexadecimal: 016D) was entered.






Powered by Atlassian Confluence and Scroll Viewport.