Here is the link (3,1)
https://www.ibm.com/docs/en/zos/3.1.0?topic=errnojrs-description-location-information
Reason codes are sometimes referred to as errnojrs or as errno2 values.
The reason code is made up of 4 bytes in the following format:
rrr
is a halfword reason
The sysomvs ctrace data is written to OMVS dataspaces (z/OS 2.4 and below) or
to 64-bit storage (above the bar) at z/OS 2.5 OR to dataset(s) defined for an
external writer.
If not using an external writer, you must capture an SVC dump of
OMVS+dataspaces.
In either case - SVC dump or dataset
Detailed OMVS tracing is described here
https://www.ibm.com/docs/en/zos/2.5.0?topic=trace-sysomvs-component
It is low-level, and will require either external writer or SVC dump of
OMVS+dataspaces to capture. Options SYSCALL and FILE will capture file
activity.
Be aware when filtering sysomvs
This link has more details about file system movement/ownership during recovery
scenarios.
https://www.ibm.com/docs/en/zos/2.4.0?topic=recovery-managing-movement-data
--
For IBM-MAIN subscribe / signoff / archive access
Check the INCLUDE/EXCLUDE parameters on the MOUNT statements in BPXPRMxx
https://www.ibm.com/docs/en/zos/2.4.0?topic=parameters-statements-bpxprmxx
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Hello Gadi - Only a TFS running as a colony address space can be extended - see
the chapter "Managing the temporary file system (TFS)" in the z/OS UNIX
Planning manual.
https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R3ga320884/$file/bpxb200_v2r3.pdf
Regards,
Dave Geib
I would start by opening SR to CommServer -
Google on 74F62104 finds this APAR - PI78033 (FIN for 2.1 and 2.2)
http://www-01.ibm.com/support/docview.wss?uid=swg1PI78033
If a BPXAS initiator is corrupted in some way, it will remain in that state
until it 'drains' (about 30 minutes after it
Please be aware of OA50872 when using IDCAMS REPRO and ZFS file systems.
http://www-01.ibm.com/support/docview.wss?crawler=1=isg1OA50872
snip from the APAR
The ONLY supported and proper use of REPRO pertaining to zFS
filesystems is to REPRO an existing zFS into a
newly defined VSAM LDS THAT HAS
