APAR status
Closed as documentation error.
Error description
z/OS UNIX System Services Documentation Updates
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of z/OS UNIX System Services for * * HBB77C0 HBB77D0 and HBB77E0 * * * **************************************************************** * PROBLEM DESCRIPTION: * * Documentation updates * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
******************** Problem #1: ******************** Book title - z/OS UNIX System Services Command Reference Book number - SA23-2280-50 Chapter - Shell Command Descriptions Section - captoinfo CASE Number - TS013447798 Initials - LMS Problem Description - We do not specify what the default processing will be if no input filename is provided Book update - Please add something similar to the following under Options filename: By default, the captoinfo command converts the termcap description for the terminal specified by the TERMCAP environment variable. If you specify the Filename parameter, the command converts all the descriptions in the file to terminfo format. If you do not specify a Filename parameter, and the TERMCAP environment variable is not set, the /usr/share/lib/termcap pathname will be used. ******************** Problem #2: ******************** Book title - z/OS UNIX System Services Planning Book number - GA32-0884-xx z/OS Releases - z/OS V2R4, V2R5, 3.1 Chapter - Using Unicode Services in a z/OS UNIX environment Section - Considerations beyond that of Enhanced ASCII CASE Number - TS012556708 Initials - XX Problem Description - Clarification Book update - Add following paragraph at the end of section of "Considerations beyond that of Enhanced ASCII" If the CCSID has multibyte character sets, partial characters may occur and Unicode Services might fail the conversion with the EIO return code. In this case, adjust the _BPXK_UNICODE_SUB, _BPXK_UNICODE_TECHNIQUE, or _BPXK_UNICODE_MAL environment variable for Unicode Services to take the appropriate conversion action. You can also turn off automatic conversion and use character-based functions such as iconv instead. ******************** Problem #3: ******************** Book title - z/OS UNIX System Services Programming Assembler Callable Services Reference Book number - SA23-2281-xx z/OS Releases - z/OS V2R4, V2R5, 3.1 Chapter - Callable services descriptions Section - BPX1RED/BPX4RED and BPX1WRT/BPX4WRT CASE Number - TS012556708 Initials - XX Problem Description - Clarification Book update - Add a Usage Note as follows: If automatic conversion is enabled with Unicode Services (ALL), see "Using Unicode Services in a z/OS UNIX environment" in "z/OS UNIX Planning" for more information. ******************** Problem #4:******************** Book title - z/OS UNIX System Services Command Reference Book number - SA23-2280-xx z/OS Releases - z/OS V2R4, V2R5, 3.1 Chapter - Appendix E. BPXCOPY Section - Parameters CASE Number - TS013088696 Initials - XX Problem Description - Clarification Book update - Add following Note statement Note: TYPE is not associated with code page conversion. If the target z/OS UNIX file previously existed and was already tagged, then code page conversion is possible, depending on the current autocvt setting for the task regardless of the TYPE value. ******************** Problem #5: ******************** Book title - UNIX System Services Command Reference Book number - SA23-2280-XX z/OS Releases - z/OS V2R4, V2R5, 3.1 Chapter - Shell Command descriptions Section - automount - Configure the automount facility CASE Number - TS014574402 Initials - CC Problem Description - #3 under usage notes. The statement about ZFS needing to be trusted led to confusion for this customer. After internal discussions we agreed to remove this statement as there are alternatives to ZFS being trusted that still allow for functionality. Book Update - Remove the following statement: The kernel address space must be trusted or mount failures will occur. For zFS file systems, the zFS started task address space must also be trusted in order to properly identify the data set as ZFS. ******************** Problem #6: ******************** Book title - Using REXX and z/OS UNIX System Services Book number - SA23-2283-XX z/OS Releases - z/OS V2R4, V2R5, 3.1 Chapter - Using TSO/E REXX for z/OS UNIX processing Section - Input and output for z/OS UNIX processing CASE Number: TS014362741 Initials - MG Problem Description: Limitations to REXX SAY directed to Stdout and stderr are not documented. EXECIO limitations are also not documented. Book Update - i) Locate the following line under subsection "Using standard Input, output, and error (file descriptors 0, 1, and 2)": If the REXX program issues a SAY instruction, the text is directed to standard output, and a newline character is appended to the end of the text. Change book to add the following to the above text: Text lines that are longer than 1023 characters are written as 1023 characters lines plus a newline char. (\nl) If you need to write text that is longer than 1023 characters without the newline characters being inserted, the write syscall allows you to do this. Example : 'write 1 Data' length(Data) ii) Under the "Using EXECIO" section: Under the Note: Add the following: When using EXECIO to write to a file, there is no maximum for the amount of characters to write and one newline character is appended to the end of the written data. *************** Problem #7: ******************** Book title - z/OS UNIX System Services Command Reference Book number - SA23-2280-xx z/OS Releases - z/OS V2R4, V2R5, 3.1 Chapter - Shell command descriptions for bpxwmigf Section - Description CASE Number - TS014868617 Initials - DHG Problem Description - the description does not state accurate authority requirements. Book Update - Change Description FROM: Use the bpxwmigf command to migrate file systems to zFS. Superuser authority is required. TO: Use the bpxwmigf command to migrate file systems to zFS. Superuser authority or READ access to the SUPERUSER.FILESYS.PFSCTL UNIXPRIV resource is required. *************** Problem #8 ******************** Book title - z/OS MVS System Management Facilities (SMF) Book number - SA38-0667-xx z/OS Releases - z/OS V2R4, V2R5, 3.1 Chapter - SMF Records Section - Record type 92 (X'5C') ? File system activity Subtype 17 CASE Number - Initials - MG Problem Description - SMF92-17 is missing a field at offset 8 and length of Reserved field should be 2 (not 3). Book Update - Change SMF 92 Subtype 17 table to 1) add new field for SMF92FAFT 2) add name for record flag bit SMF92FAIT 3) change length of Reserved field to 2 4) change offsets of SMF92FAFG and Reserved field Details are as follows: 0 0 SMF92FAWT 8 ... ... 8 8 SMF92FAFT 1 binary File type as defined in BPXYFTYP 9 9 SMF92FAFG 1 ... ... Bit Meaning when set 0 SMF92FAWT is SMF interval time (SMF92FAIT) 10 0A 2 EBCDIC Reserved 12 0C SMF92FAIN 4 ... ...
Temporary fix
Comments
APAR Information
APAR number
OA65077
Reported component name
OPENMVS SYS SRV
Reported component ID
5695SCPX1
Reported release
7C0
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-06-20
Closed date
2024-03-07
Last modified date
2026-01-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
| SA232280XX | GA320884XX | SA232281XX | SA380670XX | SA232283XX |
| SA380667X |
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19O"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"7C0"}]
Document Information
Modified date:
08 January 2026