Right now, it appears that when CMNHUTIL runs and tries to access a directory (such as root "/") that it does not have access to, it results in a S0C1 abend within CMNHUTIL with OFFSET=000010E6 within ChangeMan ZMF 7.1.1.02. This particular error, in reality, does not tell a customer much about what the problem is. I ended-up inferring that this is a problem because I happened to see that the FILEOUT= was trying to write a shell script to the root (/) directory: //WRJ2TMP EXEC PGM=CMNHUTIL, create shell command ... //SYSIN DD DATA,DLM='++' ... FILEOUT=/D67hg9r0ua6.sh ... ++

It would be helpful if certain common errors that could happen within CMNHUTIL be given in the job output to aid with better and quicker troubleshooting. The above situation would be some kind of security violation message. I'm sure that there are other situations, which currently result in an abend, that that could be coded into CMNHUTIL to give a readable error message.

Right now, it appears that when CMNHUTIL runs and tries to access a directory (such as root "/") that it does not have access to, it results in a S0C1 abend within CMNHUTIL with OFFSET=000010E6 within ChangeMan ZMF 7.1.1.02. This particular error, in reality, does not tell a customer much about what the problem is. I ended-up inferring that this is a problem because I happened to see that the FILEOUT= was trying to write a shell script to the root (/) directory: //WRJ2TMP EXEC PGM=CMNHUTIL, create shell command ... //SYSIN DD DATA,DLM='++' ... FILEOUT=/D67hg9r0ua6.sh ... ++

It would be helpful if certain common errors that could happen within CMNHUTIL be given in the job output to aid with better and quicker troubleshooting. The above situation would be some kind of security violation message. I'm sure that there are other situations, which currently result in an abend, that that could be coded into CMNHUTIL to give a readable error message.

Right now, it appears that when CMNHUTIL runs and tries to access a directory (such as root "/") that it does not have access to, it results in a S0C1 abend within CMNHUTIL with OFFSET=000010E6 within ChangeMan ZMF 7.1.1.02. This particular error, in reality, does not tell a customer much about what the problem is. I ended-up inferring that this is a problem because I happened to see that the FILEOUT= was trying to write a shell script to the root (/) directory: //WRJ2TMP EXEC PGM=CMNHUTIL, create shell command ... //SYSIN DD DATA,DLM='++' ... FILEOUT=/D67hg9r0ua6.sh ... ++

It would be helpful if certain common errors that could happen within CMNHUTIL be given in the job output to aid with better and quicker troubleshooting. The above situation would be some kind of security violation message. I'm sure that there are other situations, which currently result in an abend, that that could be coded into CMNHUTIL to give a readable error message.