Re: IKJCT43A Return Code 99 - What does this mean.
Charlie, I found this in II05243 MSGIKJ56524I COMMAND SYSTEM ERROR IKJCT43A RETURN CODE 99 IS ISSUED WHEN THE TSO/E EXEC COMMAND PROCESSOR (CLIST OR REXX EXEC) ATTEMPTS TO OPEN THE DATASET WHICH CONTAINS THE CLIST OR REXX EXEC AND FINDS THAT THE RECFM IS NOT FIXED OR VARIABLE. ACTION: FIND THE DATASET WHICH CONTAINS THE CLIST OR REXX EXEC WHICH YOU ARE ATTEMPTING TO EXECUTE AND DISPLAY THE DATASET CHARACTERISTICS. CHECK TO SEE IF THIS DATASET IS REALLY A CLIST OR REXX EXEC. Looks like one of your datasets is bad. Richard. "JONES, CHARLIE" <[EMAIL PROTECTED]To: IBM-MAIN@BAMA.UA.EDU AS.MIL> cc: Sent by: IBM Subject: IKJCT43A Return Code 99 - What does this mean. Mainframe Discussion List <[EMAIL PROTECTED] .EDU> 09/11/2006 10:04 AM Please respond to IBM Mainframe Discussion List We are testing Z/OS 1.7 I am dynamically reallocating my SYSPROC DD card with the command below: ALLOCATE FILE (SYSPROC) DATASET( 'SYS1.SCBDHENU' 'SYS3.QUICKREF.C LIST' 'SYS3.CLIST' 'SYS3.NCPS.CLIST' 'SYS1.ISP.SISPCLIB' 'SYS1.BOOKM.SEPHCLB1' 'SYS1.SCBDCLST' 'SYS1.SBLSCLI0' 'SYS1.CSF.SCSFCLI0' 'SYS3.DB2.V710107.NEW.SDSNC LST' 'SYS2.DB2.V710107.SDSNCLST' 'SYS1.ISP.SISPEXEC' 'SYS1.SBPXEXEC' 'SYS1.AOP. SAOPEXEC' 'SYS1.BOOKM.SEPHCLB1' 'SYS1.IOE.SIOEEXEC' 'SYS1.IBM.PARMLIB' 'SYS1.SH ASPARM' 'SYS1.ISP.SISPSAMP' 'SYS3.EXEC' 'SYS3.EXAMINE.CAIDBS1' 'SYS2.EXAMINE.V3 5SP01.CAIDBS2' 'SYS2.EXAMINE.V35SP01.CAICLIB' 'ZCRPSMS.XISP.TDEV.ISPCLIB' 'IDMS .DATABASE.REXX.LIB' ) SHR REUSE" When I go to SDSF and issue an SJ command on a job entry I get the following error before the JCL appears: IKJ56524I COMMAND SYSTEM ERROR+ IKJ56524I IKJCT43A RETURN CODE 99 Any ideas what this is? Charlie The contents of this e-mail are confidential. If you have received this communication by mistake, please advise the sender immediately and delete the message and any attachments. Nothing in this email designates an information system for the purposes of Section 11(a) of the New Zealand Electronic Transactions Act 2002. Westpac New Zealand Limited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: CF Structure for Health Checker
Also on a 2 system sandbox I'm seeing POLICY SIZE: 20224 K ACTUAL SIZE: 20224 K STORAGE INCREMENT SIZE: 256 K ENTRIES: IN-USE:342 TOTAL: 2571, 13% FULL ELEMENTS: IN-USE: 4383 TOTAL: 36004, 12% FULL z/OS 1.4, but only IPLd this morning if that makes any difference. Richard. Mark Zelden <[EMAIL PROTECTED]To: IBM-MAIN@BAMA.UA.EDU CHNA.COM>cc: Sent by: IBM Subject: CF Structure for Health Checker Mainframe Discussion List <[EMAIL PROTECTED] .EDU> 29/06/2006 08:23 AM Please respond to IBM Mainframe Discussion List Hi, I checked the CFSIZER tool (http://www-03.ibm.com/servers/eserver/zseries/cfsizer/) and don't see anything out there for HC log yet. According to the fine manual: "The value defined for SIZE should be no less than 8000 to ensure adequate space for check data." I am using SIZE(16000) in my 2 system sandbox and am seeing *IXC585E STRUCTURE HZS_HCHECKER_LOG IN COUPLING FACILITY nnn, PHYSICAL STRUCTURE VERSION BEEFD156 8DB22409, IS AT OR ABOVE STRUCTURE FULL MONITORING THRESHOLD OF 80%. ENTRIES: IN-USE: 1642 TOTAL: 1953, 84% FULL ELEMENTS: IN-USE: 18402 TOTAL: 23074, 79% FULL What size are others using? I am asking because as of this past weekend HC is running on all systems in one of my production sysplexes. Thanks, Mark -- Mark Zelden The contents of this e-mail are confidential. If you have received this communication by mistake, please advise the sender immediately and delete the message and any attachments. Nothing in this email designates an information system for the purposes of Section 11(a) of the New Zealand Electronic Transactions Act 2002. Westpac Banking Corporation, ABN 33 007 457 141, is incorporated in Australia -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: What the did I do wrong?
John, When we installed 3592's, we had to put some CA1 fixes on to get the CA1 CBRUXxxx exits to recognise the new media types. I've had a quick look at the code, and I don't *think* that will cause the exit to ignore the tapes, but it was only a quick look. And of course, the tapes have to be in the TMC or the exit will tell the system to ignore them. Apologies if this is stating the obvious. Richard. "McKown, John" <[EMAIL PROTECTED]To: IBM-MAIN@BAMA.UA.EDU INSCTR.COM> cc: Sent by: IBM Subject: What the did I do wrong? Mainframe Discussion List <[EMAIL PROTECTED] .EDU> 02/02/2006 10:45 AM Please respond to IBM Mainframe Discussion List I'm at the absolute end of my patience (not that I've ever had a lot of it). I've got a new 3584 library with an attached 3593-F05 (which is what the zSeries actually attaches to). I had two 3952 carts in this monster. One was in scratch status, then other in private. I ejected both of them using the LIBRARY EJECT,volser command from the console. Before doing this EJECT command, both showed up in ISMF in the library. After doing the EJECT, both disappeared from the ISMF display (The library is with "K" for Keep on the "Eject Default"). When I did a LISTC on the VOLCAT, they both showed up as being on the SHELF (as I expected). I then reinserted the volumes. There has been no change in the ISMF display, nor in the LISTC. It is as if the library did not inform the zSeries that the volumes were reinserted. If I try another EJECT, I get "volume not in library". I do have both the CBRUXEJC and CBRUXENT exits in place. They are basically the ones distributed with CA-1, with out library names in them. I am extemely frustrated with this box. The 3494-B18 that it is replacing may have been slower, but I never had these problems with it. Oh, the aforementioned exits work just fine with the 3494. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology - The contents of this e-mail are confidential. If you have received this communication by mistake, please advise the sender immediately and delete the message and any attachments. Nothing in this email designates an information system for the purposes of Section 11(a) of the New Zealand Electronic Transactions Act 2002. Westpac Banking Corporation, ABN 33 007 457 141, is incorporated in Australia - -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBMLINK News
And somebody else must be reading this list. It now says "News is currently unavailable." Richard. Alan Schwartz <[EMAIL PROTECTED]To: IBM-MAIN@BAMA.UA.EDU SURANT.COM> cc: Sent by: IBM Subject: IBMLINK News Mainframe Discussion List <[EMAIL PROTECTED] .EDU> 30/11/2005 10:22 AM Please respond to IBM Mainframe Discussion List I think IBM's lawyers took a long Thanksgiving holiday. Let's see if you see what we see. Go to Servicelink and on the right should be a link to the latest IBMLink news. Click on this and we see the latest entry is titled "TESTE". View this puppy. Someone in corporate land has a sense of humor. Alan Schwartz Assurant Shared Business Services Lead Systems Programmer Phone: 651-361-4758 Fax: 651-361-5625 - The contents of this e-mail are confidential. If you have received this communication by mistake, please advise the sender immediately and delete the message and any attachments. Nothing in this email designates an information system for the purposes of Section 11(a) of the New Zealand Electronic Transactions Act 2002. Westpac Banking Corporation, ABN 33 007 457 141, is incorporated in Australia - -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: TLS FTP
Dave, I haven't tried it with the FTP client, but our FTP server JCL looks like //FTPD PROC PARMS='', // TZ='NZST-12NZDT,M10.1.0,M3.3.0' //*** //* //* Descriptive Name:FTP Server Start Procedure //* //*** //FTPD EXEC PGM=FTPD,TIME=NOLIMIT, // PARM='POSIX(ON) ALL31(ON) ENVAR("TZ=&TZ") /&PARMS' to set the ENVAR TZ hth, Richard. Dave Gibney <[EMAIL PROTECTED]> To: IBM-MAIN@BAMA.UA.EDU Sent by: IBM cc: MainframeSubject: TLS FTP Discussion List <[EMAIL PROTECTED] .EDU> 08/06/2005 12:17 PM Please respond to IBM Mainframe Discussion List The latest FileZilla server has beta support for TLS/SSL so I thought I'd give it a try using z/OS 1.4 FTP client. It fails: EZA1701I >>> AUTH TLS 334 Using authentication type TLS EZA2897I Authentication negotiation failed The FM and IBMLINK say to turn on SSL tracing by setting an ENVAR("GSK_TRACE=0x") I can't figure how to conveniently set this for EXEC PGM=FTP in JCL. When I try ftp from OMVS, it can't seem to find my RACF keyring. I'll RFM some more tomorrow, but I thought I'd ask. I expect that we will either decide to purchase a 3rd party (ISV for M$ world) SSL capable FTP server, or something. (Https driven from batch :( But I'd like to see if I can make FileZilla work. I am aware of Open SSH, but it doesn't understand traditional MVS files and all our existing FTP jobs start with a traditional PS file. Seems a waste to copy to HFS just to SFTP out. Dave Gibney[EMAIL PROTECTED] System Programmer(509) 335-7359 Information Technology Washington State University Pullman, WA 99164-1222 - The contents of this e-mail are confidential. If you have received this communication by mistake, please advise the sender immediately and delete the message and any attachments. Nothing in this email designates an information system for the purposes of Section 11(a) of the New Zealand Electronic Transactions Act 2002. Westpac Banking Corporation, ABN 33 007 457 141, is incorporated in Australia - -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html