Status codes in PCB mask in Linkage section

operation code

All blank/spaces
GE
GB

GA
‘GU’, ‘GN’,
or ‘GNP’ call GK
DA

Replace RX
II
Insert GE
DA
DJ
Delete DX

GG
 Status codes in PCB mask in Linkage section
Reason
Successful

no segment found. This could happen after a ‘GU’, ‘GN’, or ‘GNP’ call.
end of database
which means DL/I has returned a segment, but that the segment is at a higher level in the hierarchy than the last returned
segment. DL/I will only return ‘GA’ for UNQUALIFIED GET NEXT calls
which means DL/I returned a segment that satisfies an UNQUALIFIED ‘GN’ or ‘GNP’ call, but the segment is a different
segment type than the last segment that was returned (but at the same level).
means you tried to change the Key field of the segment.
means you violated some REPLACE rule. Once case would be if you issued a GET call rather than a GET HOLD call before
issuing the REPL call, or you may have tried to improperly use a COMMAND CODE in a REPL call.
tried to insert a segment that already exists.
could not find the path of segment specified in our SSAs
unsuccessful – the segment key was changed before DLET was issued.
unsuccessful – the program did not issue a GET HOLD call before the DLET was issued.
unsuccessful – the program issued a DLET call which violated the delete rule defined for the segment in the DBD
DL/I returns this status code if the segment being retrieved
contains an invalid pointer and the application program has a processing
option of GOT or GON. This can occur when update activity in the database is going on ncurrently with your program's
processing.
 FUNCTION codes in Working storage section
CODE MEANING DESCRIPTION
GU Get-unique To obtain a unique occurrence of a segment within a database
GN Get-next To obtain the next occurrence of a segment within a database
Get-next-within- To obtain the next occurrence of a segment under a parent; retrieves
GNP parent child segments under a parent sequentially
GHU Get-hold-unique
The GET_HOLD function codes are identical to the GET codes except that
GHN Get-hold-next they must be used for retrieval if you intent to ALTER the data are being
Get-hold-next- retrieved.NOTE: these codes imply exclusive use of the segment; no one
GHNP else can access the segment until you are finished with it.
within-parent
ISRT insert insert data
REPL replace update data
DELT delete delete data
 Valid PROCOPTs in PCB defenition in PSB
code Usage
Get function. If a database is shared at the database level when
PROCOPT=G, DBRC grants access with read integrity. It prevents other pgm cannot update DB
the concurrent execution of the application program and the
updating by the IMS subsystem.
G
I INSERT
D DELETE
R REPLACE
A all options (G,I,R,D)
K access to only the KEY of the segment

for ONLY: used with G to indicate that get hold calls are not
allowed.
Read only. (Use this code with G.) If a database is shared at the other pgm can update DB
database level when PROCOPT=GO, DBRC grants access without
read integrity. It enables the application program to run and the
IMS subsystem to update the database concurrently.
O
P PATH calls
LOAD (initial load of data)
L

Read only. (Use this code with GO.) N allows the application
program to avoid abends when referring to data that is being
updated by another program. A GG status code is returned, and
the program must decide whether to end or to continue.
N
Read Only. (Use this code with GO.) T works similarly as N, except
that it causes DL/I to retry the operation automatically before
T returning the GG status code.

enables exclusive use of the database or segment. (Use this code

with G.) If a database is shared at the database level when
PROCOPT=GE, DBRC grants exclusive use to the database
E
 Valid Command codes in SSA
code Usage
D Retrive path
F Access first segment occurance
L Access last segment occurance
U Maintain current position at this level
V Maintain current position at this and higher levels
N Do not replace this segment
C Use a concatenated key
P Establish parentage at this level
_ Null/ignore