Determine whether your system has z/OS UNIX program files with certain attributes
Description
Before z/OS V2R2 and without the PTFs for APAR OA45793 installed, the sticky attribute was honored when either the set-user-id or set-group-id attributes were set. Starting with z/OS V2R2, APAR OA45793 changes the behavior of the exec (BPX1EXC or BPX4EXC) and spawn (BPX1SPN or BPX4SPN) interfaces when the user-specified path name resolves to a file that has the sticky attribute and either the set-user-id or set-group-id attributes. The exec and spawn services now ignore the sticky attribute unless a new RACF FACILITY class profile indicates that the usage is acceptable. Ignoring the sticky attribute means that the MVS program search order will not be used to locate the target program; only the z/OS UNIX program file that is identified by the user-specified path name is used.
EC6 abends with reason code xxxxE055 occur if the program is found in the MVS program search and no matching FACILITY class profile is found. If the program is not found in the MVS program search order, the z/OS UNIX file is run, which is the current behavior of exec and spawn.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | z/OS UNIX |
|---|---|
| When change was introduced: | z/OS V2R1, z/OS V1R13, and z/OS V1R12, all with APAR OA45793 applied. |
| Applies to migration from: | z/OS V2R1 and z/OS V1R13 both without APAR OA45793 applied. |
| Timing: | Before installing z/OS V2R2. |
| Is the migration action required? | Yes, if you have a program that fits the criteria in the Steps to take section. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | None. |
| Related IBM® Health Checker for z/OS® check: | None. |
Steps to take
- Determine whether any of your program files have the sticky attribute
and either the set-user-id or set-group-id attributes. For each program
file that has the sticky attribute and either the set-user-id or set-group-id
attribute, select one of the following actions:
- If you do not want the exec and spawn services to use the MVS search order to locate programs, you do not need to take any action.
- If you want the exec and spawn services to always use the MVS
search order for certain programs, then specify:
BPX.STICKYSUG.YOURPGM BPX.STICKYSUG.MYPGM - If you want the exec and spawn services to use the MVS search
order for a group of commonly named programs, then define a generic
profile:
The exec and spawn services will use the MVS search order for any program that begins with the characters MYP. The minimum allowable generic file is BPX.STICKYSUG.*.BPX.STICKYSUG.MYP*
After you complete the steps, you have determined how program files that have the sticky attribute and either the set-user-id or set-group-id attributes are to be handled.
Reference information
For more information, see z/OS UNIX System Services Programming: Assembler Callable Services Reference.