LinkedIn Poll: Are you considering Linux on z?
If you have a LinkedIn account, please participate in my poll to determine Linux on z penetration. Feel free to comment here or on LinkedIn also. http://polls.linkedin.com/p/81429/kyqic Thanks Alan Harrison http://practicallysecure.blogspot.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
OPUT failed BPXF106E - USS space?
I'm trying to copy a 20MB tar file up to my USS file system. I'm getting this error. BPXF106E RETURN CODE 0085, REASON CODE 5B4FC005. AN ERROR OCCURRED DURING THE WRITING TO HFS FILE /itim/racf.tar. The command that ends with this error is "OPUT 'USER.ITIM.TAR' '/itim/racf.tar' BINARY " Reason code x85 appears to be space, but there's plenty of room on the volume, the file is about 20MB. Am I hitting some system limit or user quota? If so how do I lift that? Thanks Alan. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Space error copying file to OMVS (z/OS USS) ?
I'm having trouble with OPUT in that I'm getting this BPXF106E RETURN CODE 0085, REASON CODE 5B4FC005. AN ERROR OCCURRED DURING THE WRITING TO HFS FILE /itim/racf.tar. This is described here:- http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2M381/SPTM004092 and that points to the reason codes here:- http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/BPXZA880/3.0?DT=20070606153306 where error code 85 is described as No space is left on the device, or no space is available to create the IPC member ID. There should be plenty of space, Z9USS1 has 230 free cyls and this is a 20MB file (373 tracks)! Is there a quota setting in OMVS on the ADCD ver 1.9? Where is the "IPC member ID" stored? Thanks Alan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
System z Security Vulnerabilities
I've been involved in a long discussion on LinkedIn about mainframe vulnerabilities. We are discussing whether a central repository of common configuration errors is a good idea. I have created a Wiki on IBM developerWorks which we System z Security experts could fill up with common RACF errors and z/OS configuration tips, with which System z users worldwide could check and harden their own installations. Please visit my developerWorks blog "zSecurity" here http://j.mp/aDJp10 to read the full story including links back to the original LinkedIn discussion, and then feel free to comment. Many Thanks Alan Harrison, CISSP, System z Technical Specialist Pirean Ltd. www.pirean.com/systemz -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: System z Security Vulnerabilities
Thanks guys. Some clarification. 1. For those nervous about shortened URLs, my blog is indeed at https://www.ibm.com/developerworks/mydeveloperworks/blogs/zSecurity/ 2. If you read the LinkedIn discussion (you can find a link in the blog post) and the blog post itself you'll see I'm not talking about vulnerabilities in the code base. I'm talking about insecure configurations, people NOT locking down the mainframe correctly despite the controls being documented and available. People who still have not secured all their APF libraries, for example, or people with NODES definitions from 25 years ago for nodes that have long since ceased to be, and lots of UACC(UPDATE). Thanks again. Alan. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
