BPXF024I
You get this message if the syslogd program is not running.
BPXP015I HFS PROGRAM /usr/lpp/zosmf/lib/libIzuCommandJni.so IS NOT MARKED PROGRAM CONTROLLED. BPXP014I ENVIRONMENT MUST BE CONTROLLED FOR DAEMON (BPX.DAEMON) PROCESSING.
Use the command extattr /usr/lpp/zosmf/lib/libIzuCommandJni.so to check the Program Controlled attribute is set. Use the extattr +p…. to set it if required.
I had the wrong SAF_PREFIX(‘IZUDFLT‘) in USER.Z24A.PARMLIB(IZUPRMCP). IZUDFLT was correct.
I had other problems like invalid password when I logged onto the web browser.
Fix the problem and regenerate.
BPXO042I with D OMVS,PFS
I was expecing D OMVS,PFS or D OMVS,P to give me BPXO068I and a list of Physical File Systems.
it gives BPXO042I when the command failed.
This was due to having an HFS definition in my z/OS 3.1 system. HFS is not supported on 3.1 . I removed the definition and it worked.
BPX1SOC TTLS_INIT_CONNECTION rv -1 rc ECONNRESET(1121) rs 2007593789 (0x77a9733d) 77a9733d EDC8121I Connection reset
The bpxmtext 77a9733d gives
TCPIP
JrTtlsHandshakeFailed: AT-TLS was unable to successfully negotiate a secure
TCP connection with the remote end.
Action: Review message EZD1286I for more information about the error.
On syslog was
EZD1287I TTLS Error RC: 403 Initial Handshake
Where 403 is The required certificate was not received from the communication partner.
The Wireshark output had a Certificate flow from the client to the server. This had no certificate in it.
The reason for this was,
- the client had an RSA certificate
- the Signature Hash Algorithms sent from the server did not include RSA.
The client was thus unable to send a certificate matching the SHA.
If I specified RSA only signature pairs, I could only use an RSA certificate. An Elliptic Curve certificate (ECDSA) had the same message and error code.
BPX1BND rv -1 rc EADDRINUSE(1115) rs 1951167047 (0x744c7247) EDC8115I Address already in use.
Because a program may not know that the “FIN” (end of conversation) has got to the other end, a socket enters a TIMEWAIT state. The IBM documentation says
If the server cannot wait for one to four minutes, you can use the setsockopt() call in the server to specify SO_REUSEADDR before it issues the bind() call. In that case, the server will be able to bind its socket to the same port number it was using before, even if the TIMEWAIT period has not elapsed. However, the TCP protocol layer still prevents it from establishing a connection to the same partner socket address. As clients normally initiate connections and clients use ephemeral port numbers, the likelihood of this is low.
BPX1SND rv -1 rc EOPNOTSUPP(1112) rs 1977578120 (0x75df7288) EDC8112I Operation not supported on socket.
I got this trying to issue bpx1snd() when there was data in the receive buffer. I used bpx1rcv to read the data, and the problem went away.
I peeked at the data before getting it, so I knew the length of the data to get, and so avoided waiting for data.
char buf[4000];
int lbuff = sizeof(buf);
int alet = 0;
int flags = MSG_PEEK;
BPX1RCV( &sd, // socket desciptor
&lbuff,
&buf,
&alet,
&flags,
&rv, // -1 or number of bytes
&rc,
&rs);
printf("BPX1RCV Peek bytes %d data... n",rv );
lbuff = rv; // the number of bytes in the buffer
flags = 0 ;
BPX1RCV( &sd, // socket descriptor
&lbuff,
&buf,
&alet,
&flags,
&rv, // -1 or number of bytes
&rc,
&rs);
printf("BPX1RCV bytes %d data... n",rv );
BPXF135E RETURN CODE 00000079, REASON CODE 055B005C
I got this using the command
MOUNT FILESYSTEM(‘COLIN.ZFS2’) TYPE(ZFS) MOUNTPOINT(‘/u/ibmuser/temp’ )
code 79 is invalid. The 005b005c means already in use. Either
- COLIN.ZFS2 is already mounted
- there is something else mounted on /u/ibmuser/temp
You can use the D OMVS,F command to display the file system and where they are mounted.
BPXF135E RETURN CODE 00000081, REASON CODE 053B006C
May because the file system is mounted READ and it needs to be RDWR.
BPXMTEXT 053B006C -> JRFileNotThere: The requested file does not exist.
Problem 1
I had MOUNTPOINT(‘/u/ibmuser/test’ ) (which did not exit) not the correct MOUNTPOINT(‘/u/ibmuser/temp’ )
Problem 2
I was trying to mount it at /my. I had to go into Unix and issue mkdir /my only then could I mount the file system.
BPXF137E RETURN CODE 00000079, REASON CODE 0588002E.
THE UNMOUNT FAILED FOR FILE SYSTEM …
002E is JRFilesysNotThere. Check the file system is mounted
BPXF137E RETURN CODE 00000072, REASON CODE 058800AA
BPXF137E RETURN CODE 00000072 (the resource is busy) , REASON CODE 058800AA JRFsParentFs The file system has file systems mounted on it.
I was trying to unmount a ZFS file systemm, and got the above messages. It means you cannot unmount it, because you have other file systems attached to it. On the z/OS console it had
BPXF271I FILE SYSTEM ZFS.USERS
FAILED TO UNMOUNT BECAUSE IT CONTAINS MOUNTPOINT DIRECTORIES FOR
ONE OR MORE OTHER FILE SYSTEMS WHICH MUST BE UNMOUNTED FIRST,
INCLUDING FILE SYSTEM COLIN.ZFS2
I used
unmount filesystem('COLIN.ZFS2') Immediate
and got message on the console
IOEZ00048I Detaching aggregate COLIN.ZFS2
BPXF002I FILE SYSTEM … NOT MOUNTED. RETURN CODE = 0000009D, REASON CODE = 11B900B7
With a Physical File System (PFS) there was a bad parameter in the OSI_THREAD block. The value of threadParm.ot_modname ( program to execute) did not exist.