Troubleshooting
Problem
Applications, such as OMPROUTE, SYSLOGD, FTPD, and NAMED might fail with an 0C1 abend during startup if the sticky bit isn't turned on in the HFS. This occurs when the program is started using the HFS filename. The abend does not occur if the program is started using an EXEC JCL statement referring to its PDS(E) member name.
Cause
Applications are abending with a s0C1 when they are started. Data from the abend is:
ACTIVE LOAD MODULE ADDRESS=12508F80 OFFSET=00000002 NAME=SPECIALNAME 61A4A299 61939797 61A38397 899761A2 */usr/lpp/tcpip/s* 82899561 96949799 96A4A385 *bin/omproute * DATA AT PSW 12508F7C - 00000000 0000E388 89A24086
In this case, the program being executed is OMPROUTE, located in /usr/lpp/tcpip/sbin/omproute.
The abend occurs because the sticky bit is not turned on for this application. The sticky bit tells OMVS to search for the program in the user's STEPLIB, the link pack area, or the link list concatenation. When the sticky bit is not on, OMVS tries to execute the data it finds in the HFS. This is not executable code, which causes the 0c1 abend.
Resolving The Problem
The sticky bit can be displayed by using the ls command. The UNIX System Services User's Guide has more information on displaying and setting the sticky bit with the chmod command. For example, the sticky bit for SYSLOGD can be turned on with this command:
chmod o+t /usr/lpp/tcpip/sbin/syslogd
Turning the sticky bit on eliminates the 0c1 abend.
For z/OS 1.4 and below, if the RESTFS job (run during a Serverpac install) is not run from a uid=0 id, the sticky bit is not turned on for programs in the /usr/lpp/tcpip/sbin directory and other directories. This job must be run from a userid with uid=0. Refer to the ServerPac: Installing Your Order manual for more information on the RESTFS job.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21107043