File control trace points (AP 0B50 - AP 0BF2)
This table lists the file control trace points in the range AP 0B50 to AP 0BF2. The table includes the trace ID, the module name, the trace level, the trace type, and the data returned by the trace point.
For more file control trace entries, see File control trace points (AP 0410 - AP 04FB) and File control trace points (AP 2300 - AP 24E1).
Point ID | Module | Lvl | Type | Data |
---|---|---|---|---|
AP 0B50 | DFHFCAT | FC 1 | Entry |
|
AP 0B51 | DFHFCAT | FC 1 | Exit |
|
AP 0B52 | DFHFCAT | Exc | Invalid format |
|
AP 0B53 | DFHFCAT | Exc | Invalid function |
|
AP 0B54 | DFHFCAT | Exc | Recovery routine |
|
AP 0B55 | DFHFCAT | Exc | Change mode failed |
|
AP 0B56 | DFHFCAT | Exc | Backup while open not supported |
|
AP 0B57 | DFHFCAT | Exc | Inquire on whether DSN is SMS-managed failed |
|
AP 0B58 | DFHFCAT | Exc | DSN not known |
|
AP 0B59 | DFHFCAT | Exc | Set RECOVERED error |
|
AP 0B5A | DFHFCAT | Exc | Set recovery point error |
|
AP 0B5B | DFHFCAT | Exc | Set BWO disabled failed |
|
AP 0B5C | DFHFCAT | Exc | Inquire BWO enabled failed |
|
AP 0B5D | DFHFCAT | Exc | Set BWO enabled failed |
|
AP 0B5E | DFHFCAT | Exc | Restore and forward recovery needed |
|
AP 0B5F | DFHFCAT | Exc | Forward recovery needed |
|
AP 0B60 | DFHFCSD | FC 1 | Entry |
|
AP 0B61 | DFHFCSD | FC 1 | Exit |
|
AP 0B62 | DFHFCSD | Exc | Invalid format |
|
AP 0B63 | DFHFCSD | Exc | Invalid function |
|
AP 0B64 | DFHFCSD | Exc | Recovery |
|
AP 0B65 | DFHFCSD | Exc | File close error |
|
AP 0B66 | DFHFCSD | Exc | TM get next failed |
|
AP 0B67 | DFHFCSD | Exc | A bad response was returned by the Lock Manager |
|
AP 0B70 | DFHFCAT | Exc | DFHSM/DFDSS back level |
|
AP 0B71 | DFHFCRS | FC 2 | Entry |
|
AP 0B72 | DFHFCRS | FC 2 | Exit |
|
AP 0B73 | DFHFCRS | Exc | Recovery routine entered |
|
AP 0B74 | DFHFCRS | Exc | Purged |
|
AP 0B75 | DFHFCRS | Exc | DFHDSSR call failed |
|
AP 0B76 | DFHFCRS | Exc | DFHRMRE call failed |
|
AP 0B77 | DFHFCRV | FC 2 | About to call VSAM |
|
AP 0B78 | DFHFCRV | FC 2 | Return from VSAM |
|
AP 0B79 | DFHFCRV | FC 2 | Enter RLSWAIT exit |
|
AP 0B7A | DFHFCRV | FC 2 | Exit RLSWAIT exit |
|
AP 0B7B | DFHFCRV | Exc | VSAM detected error |
|
AP 0B7C | DFHFCRV | Exc | Recovery |
|
AP 0B7D | DFHFCRV | Exc | Purged | |
AP 0B7E | DFHFCRV | Exc | DFHDSSR call failed |
|
AP 0B80 | DFHFCCA | FC 1 | Entry |
|
AP 0B81 | DFHFCCA | FC 1 | Exit |
|
AP 0B82 | DFHFCCA | Exc | Invalid format |
|
AP 0B83 | DFHFCCA | Exc | Invalid function |
|
AP 0B84 | DFHFCCA | Exc | Recovery |
|
AP 0B85 | DFHFCCA | FC 2 | ACB before VSAM |
|
AP 0B86 | DFHFCCA | FC 2 | ACB after VSAM |
|
AP 0B87 | DFHFCCA | Exc | ACB request error |
|
AP 0B88 | DFHFCCA | FC 2 | RPL before VSAM |
|
AP 0B89 | DFHFCCA | FC 2 | RPL after VSAM |
|
AP 0B8A | DFHFCCA | Exc | VSAM detected error |
|
AP 0B8B | DFHFCCA | Exc | DFHDSSR call failed |
|
AP 0B8C | DFHFCCA | FC 2 | Enter RLSWAIT exit |
|
AP 0B8D | DFHFCCA | FC 2 | Exit RLSWAIT exit |
|
AP 0B8E | DFHFCCA | Exc | Purged |
|
AP 0B8F | DFHFCCA | Exc | DFHXMAT call failed |
|
AP 0B90 | DFHFCCA | FC 2 | ACB Before GENCB |
|
AP 0B91 | DFHFCCA | FC 2 | ACB After GENCB |
|
AP 0B92 | DFHFCCA | Exc | GENCB VSAM error |
|
AP 0B93 | DFHFCCA | FC 2 | ACB Before IDAREGP |
|
AP 0B94 | DFHFCCA | FC 2 | ACB After IDAREGP |
|
AP 0B95 | DFHFCCA | FC 2 | ACB Before IDAUNRP |
|
AP 0B96 | DFHFCCA | FC 2 | ACB After IDAUNRP |
|
AP 0B97 | DFHFCCA | Exc | REG VSAM error |
|
AP 0B98 | DFHFCCA | Exc | UNREG VSAM error |
|
AP 0B99 | DFHFCCA | Exc | A bad response was returned by the Lock Manager |
|
AP 0B9A | DFHFCCA | Exc | A bad response was returned by the Dispatch Domain |
|
AP 0BA0 | DFHFCRO | FC 2 | Entry |
|
AP 0BA1 | DFHFCRO | FC 2 | Exit |
|
AP 0BA2 | DFHFCRO | Exc | Invalid request |
|
AP 0BA3 | DFHFCRO | Exc | Recovery |
|
AP 0BA4 | DFHFCRO | Exc | Disaster |
|
AP 0BA5 | DFHFCRO | Exc | Purged |
|
AP 0BA6 | DFHFCRO | Exc | VSAM Error |
|
AP 0BA7 | DFHFCRO | Exc | Getmain failed |
|
AP 0BA9 | DFHFCRO | FC 2 | Call VSAM |
|
AP 0BAA | DFHFCRO | FC 2 | Return from VSAM |
|
AP 0BAB | DFHFCRO | FC 2 | Locate volume before |
|
AP 0BAC | DFHFCRO | FC 2 | Locate volume after |
|
AP 0BB0 | DFHFCIR | FC 1 | Entry |
|
AP 0BB1 | DFHFCIR | FC 1 | Exit |
|
AP 0BB2 | DFHFCIR | Exc | Invalid format |
|
AP 0BB3 | DFHFCIR | Exc | Invalid function |
|
AP 0BB4 | DFHFCIR | Exc | Recovery routine |
|
AP 0BB7 | DFHFCIR | Exc | Inadequate parameter list supplied |
|
AP 0BB8 | DFHFCIR | Exc | Table manager locate for FCTE returned not found |
|
AP 0BB9 | DFHFCIR | Exc | Table manager locate for FCTE returned serious error |
|
AP 0BBA | DFHFCIR | Exc | Table manager unlock for FCTE returned not found |
|
AP 0BBB | DFHFCIR | Exc | Table manager unlock for FCTE returned serious error |
|
AP 0BBC | DFHFCIR | Exc | Enqueue error on acquiring retained CICS® |
|
AP 0BBD | DFHFCIR | Exc | Unrecognized data set type code |
|
AP 0BBE | DFHFCIR | Exc | DFHRMRE call failed |
|
AP 0BCG | DFHFCLJ | LG 1 | Buffer length error |
|
AP 0BC0 | DFHFCLJ | FC 2 | Entry |
|
AP 0BC1 | DFHFCLJ | FC 2 | Exit |
|
AP 0BC2 | DFHFCLJ | Exc | Invalid format |
|
AP 0BC3 | DFHFCLJ | Exc | Invalid function |
|
AP 0BC4 | DFHFCLJ | Exc | Recovery |
|
AP 0BC5 | DFHFCLJ | Exc | Table manager GETNEXT failure |
|
AP 0BC6 | DFHFCLJ | Exc | Recovery manager append failure |
|
AP 0BC7 | DFHFCLJ | Exc | Recovery manager force failure |
|
AP 0BC8 | DFHFCLJ | Exc | Buffer length error |
|
AP 0BD0 | DFHFCES | FC 1 | Entry |
|
AP 0BD1 | DFHFCES | FC 1 | Exit |
|
AP 0BD2 | DFHFCES | Exc | Invalid format |
|
AP 0BD3 | DFHFCES | Exc | Invalid function |
|
AP 0BD4 | DFHFCES | Exc | Recovery routine |
|
AP 0BD5 | DFHFCES | Exc | Disaster |
|
AP 0BD6 | DFHFCES | Exc | Purged |
|
AP 0BD7 | DFHFCES | Exc | Transaction environment error |
|
AP 0BE0 | DFHFCRC | FC 1 | Entry |
|
AP 0BE1 | DFHFCRC | FC 1 | Exit |
|
AP 0BE2 | DFHFCRC | Exc | Invalid format |
|
AP 0BE3 | DFHFCRC | Exc | Invalid function |
|
AP 0BE4 | DFHFCRC | Exc | Recovery routine |
|
AP 0BE7 | DFHFCRC | Exc | Invalid log record type |
|
AP 0BE8 | DFHFCRC | Exc | Invalid file name in log record |
|
AP 0BE9 | DFHFCRC | Exc | Invalid LUWID |
|
AP 0BEA | DFHFCRC | Exc | Unretained FLAB found on unshunt |
|
AP 0BEB | DFHFCRC | Exc | Release locks exception |
|
AP 0BEC | DFHFCRC | Exc | Retain locks exception |
|
AP 0BED | DFHFCRC | Exc | Unexpected backout failure |
|
AP 0BEE | DFHFCRC | Exc | Lost locks complete error |
|
AP 0BEF | DFHFCRC | Exc | Backout failure |
|
AP 0BF0 | DFHFCRC | Exc | Exception from FCFR Prepare |
|
AP 0BF1 | DFHFCRC | Exc | Transaction attach error |
|
AP 0BF2 | DFHFCRC | Exc | No work token |
|
Format of data fields 2, 3, and 4 from DFHFCLJ
Data field 1 contains the FCLJ parameter
list in all cases. The contents of data fields 2, 3, and 4 depend
on the function performed by DFHFCLJ:
- Function
- Contents of data fields
- File Open
- Data field 2 contains the complete tie-up record. This comprises data that is general to all log records followed by data specific to tie-up records. Data fields 3 and 4 are not used.
- Data Set Copy
- Data fields 2, 3, and 4 are as for File Open
- File Close
- Data field 2 contains the complete file close record. This comprises data general to all log records followed by data specific to file close records. Data fields 3 and 4 are not used.
- Read Only
- Data field 2 contains the fixed-length part of the log record. This comprises data that is general to all log records followed by data that is particular to just the records being accessed. Data field 3 contains the key of access. Data field 4 contains the first 80 bytes of the record being accessed.
- Read Update
- Data fields 2, 3, and 4 are as for Read Only
- Write Update
- Data fields 2, 3, and 4 are as for Read Only
- Write Add
- Data fields 2, 3, and 4 are as for Read Only
- Write Add Complete
- Data fields 2, 3, and 4 are as for Read Only. However, if the Write Add Complete is to an ESDS, data fields 3 and 4 are not used.
- Write Delete
- Data field 2 contains the fixed-length part of the log record. This comprises data that is general to all log records, followed by data that is specific to Write Delete records. Data field 3 contains the base key. Data field 4 contains the path key.
- Take Keypoint
- Data fields 2, 3, and 4 are not used.
- Synchronize Read Update
- Data fields 2, 3, and 4 are not used.