Re: Extending the /tmp file system
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 z/OS UNIX Support -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Can you use IDCAMS REPRO on zFS files
Please be aware of OA50872 when using IDCAMS REPRO and ZFS file systems. http://www-01.ibm.com/support/docview.wss?crawler=1&uid=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 NOT HAD THE IOEAGFMT UTILITY run against it to make it a viable zFS filesystem. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Abend CODE=4C5 REASON CODE=74F62104
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 goes idle), or is ended by the 'f bpxoinit,shutdown=forkinit' command. WLM should then start a new instance of BPXAS on demand (fork). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: OMVS File System Automove question
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: OMVS File System Automove question
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 instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unix System Services - strace
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 ctrace by jobname - The JOBNAME= parameter can be used for the SYSOMVS Ctrace to trace data just for jobs that run with the specific user ID(s) specified in the JOBNAME list. This filtering is based on the user ID of a job, not its jobname. The OMVS kernel is traced with jobname OMVS. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unix System Services - strace
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 from external writer - you must then use IPCS to format the ctrace. (aplogies for not mentioning this in the prior post) IPCS option 2.7.1 provides a panel to build the command to format the ctrace. Command line (IPCS option 6) would bectrace comp(sysomvs) local full options((kerninfo)) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Hex error code interpreter?
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 code qualifier. Generally this is used to identify the issuing module and represents a module ID. is the halfword reason code that is described in this documentation. Only this part of the reason code is intended as an interface for programmers. If the contents of the two high-order bytes are within the range of X'' – X'20FF' the error that is represented by the reason code is provided in this documentation. The two high-order bytes of the reason codes returned contain a value that is used to qualify the contents of the two low-order bytes. If the contents of the two high-order bytes are outside the range, the error that is represented by the reason code is not a z/OS UNIX reason code. Use Table 1 to determine where additional information on the reason code can be found. For z/OS® UNIX, zFS, TCP/IP and Language Environment® reason codes, users can use either the BPXMTEXT TSO/E command or the bpxmtext shell command to display a reason code's meaning and recommended action. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
