Re: IEFUJI problem, preventing TSO logon
SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI As has been pointed out, the exit name is not IEFUJI. It might be SYS.IEFUJI, it might be SYSSTC.IEFUJI, it might be SYSTSO.IEFUJI (or others). This is all documented and depends on how you defined IEFUJI with your SMFPRMxx definition. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
You could call me Ray, or you could call me Ray Jay, or you could call me Ray Jay Johnson. But you doesn't has to call me Johnson. --- rel...@us.ibm.com wrote: From: Peter Relson rel...@us.ibm.com To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEFUJI problem, preventing TSO logon Date: Fri, 27 Jun 2014 10:19:56 -0400 SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI As has been pointed out, the exit name is not IEFUJI. It might be SYS.IEFUJI, it might be SYSSTC.IEFUJI, it might be SYSTSO.IEFUJI (or others). This is all documented and depends on how you defined IEFUJI with your SMFPRMxx definition. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN _ Netscape. Just the Net You Need. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IEFUJI problem, preventing TSO logon
I have this situation/condition. I installed an IEFUJI exit and it is preventing logon to TSO, and I can not figure out how to remedy this situation. I receive the following series of messages when attempting logon. IKJ56455I SPJRJ LOGON IN PROGRESS AT 11:38:42 ON JUNE 25, 2014 IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE IKJ56470I SPJRJ LOGGED OFF TSO AT 11:38:42 ON JUNE 25, 2014 ACF82931 ACF2, LOGON ATTEMPT FAILED. SEE MESSAGE MANUAL FOR POSSIBLE CAUSES ACF82904 ACF2, SESSION TERMINATED. I have attempted to delete the exit, i.e. SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI. This results in: CSV421I MODULE IEFUJI WAS NOT DELETED FROM EXIT IEFUJI. EXIT NOT DEFINED br / br / br / br / ** BMI DISCLAIMER ** This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
How was the exit installed IPL or SETPROG? If IPL, is the exit defined in PROGxx? (based on the CSV421I message) Is there an EXIT statement for IEFUJI in PROGxx? If installed via IPL and not in PROGxx, replace the exit with a renamed copy of IEFBR14 and re-ipl Is it possible this is just a ordinary JCL error in the logon proc? What does the console log say? You have shown the tso terminal messages and the output of the setprog command, but not what the log has said about the logon. If ACF2, there should be some messages on the console log, indicating possible causes of failure. snip I have this situation/condition. I installed an IEFUJI exit and it is preventing logon to TSO, and I can not figure out how to remedy this situation. I receive the following series of messages when attempting logon. IKJ56455I SPJRJ LOGON IN PROGRESS AT 11:38:42 ON JUNE 25, 2014 IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE IKJ56470I SPJRJ LOGGED OFF TSO AT 11:38:42 ON JUNE 25, 2014 ACF82931 ACF2, LOGON ATTEMPT FAILED. SEE MESSAGE MANUAL FOR POSSIBLE CAUSES ACF82904 ACF2, SESSION TERMINATED. I have attempted to delete the exit, i.e. SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI. This results in: CSV421I MODULE IEFUJI WAS NOT DELETED FROM EXIT IEFUJI. EXIT NOT DEFINED /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
Which exit point did you install it at - SYS.IEFUJI or SYSTSO.IEFUJI D PROG,EXIT,EN=SYS.IEFUJI,DIAG D PROG,EXIT,EN=SYSTSO.IEFUJI.DIAG may help. Andrew Metcalfe | Systems Programming Team | Global Technology Infrastructure Services This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC. Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority (Financial Services Register No. 122702). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
Jackson, Robin wrote: I have this situation/condition. I installed an IEFUJI exit and it is preventing logon to TSO, and I can not figure out how to remedy this situation. I receive the following series of messages when attempting logon. I have attempted to delete the exit, i.e. SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI. This results in: CSV421I MODULE IEFUJI WAS NOT DELETED FROM EXIT IEFUJI. EXIT NOT DEFINED No, create a new SMFPRMxx without any references to IEFUJI and do a T SMF=xx. Then check the other's replies to fix your problem including your SETPROG EXIT. War story: I got many times in such troubles in my sandbox. It helps to have a spare SMFPRMxx and PROGxx members just for that. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
This message: IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE denotes that a dataset on a DD stmt in the LOGON proc could not be allocated.. Check all allocation names and spelling. John Clifford On Thu, Jun 26, 2014 at 9:42 AM, Jackson, Robin rjacks...@bmi.com wrote: I have this situation/condition. I installed an IEFUJI exit and it is preventing logon to TSO, and I can not figure out how to remedy this situation. I receive the following series of messages when attempting logon. IKJ56455I SPJRJ LOGON IN PROGRESS AT 11:38:42 ON JUNE 25, 2014 IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE IKJ56470I SPJRJ LOGGED OFF TSO AT 11:38:42 ON JUNE 25, 2014 ACF82931 ACF2, LOGON ATTEMPT FAILED. SEE MESSAGE MANUAL FOR POSSIBLE CAUSES ACF82904 ACF2, SESSION TERMINATED. I have attempted to delete the exit, i.e. SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI. This results in: CSV421I MODULE IEFUJI WAS NOT DELETED FROM EXIT IEFUJI. EXIT NOT DEFINED br / br / br / br / ** BMI DISCLAIMER ** This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
John Clifford wrote: IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE denotes that a dataset on a DD stmt in the LOGON proc could not be allocated. Check all allocation names and spelling. Excellent catch which I initially overlooked. Just wondering whether the new exit is causing this problem with the DD. Anyways, it also helps to have a spare logon proc just for this trouble. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
Likewise, I have shot myself in a lower extremity when creating/modifying a logon proc. A once old timer advised while still in edit, submit it. JCL errors will occur then as opposed to later. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Thursday, June 26, 2014 10:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEFUJI problem, preventing TSO logon John Clifford wrote: IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE denotes that a dataset on a DD stmt in the LOGON proc could not be allocated. Check all allocation names and spelling. Excellent catch which I initially overlooked. Just wondering whether the new exit is causing this problem with the DD. Anyways, it also helps to have a spare logon proc just for this trouble. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
The major problem that I have is I can NOT logon to TSO to make any changes. Thanks, Rob Jackson Mainframe Systems Programming Information Services Group 10 Music Square East, Nashville, TN 37203 (615) 401-2248 (o) (615) 689-1435 (c) email: rjacks...@bmi.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Thursday, June 26, 2014 10:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEFUJI problem, preventing TSO logon Jackson, Robin wrote: I have this situation/condition. I installed an IEFUJI exit and it is preventing logon to TSO, and I can not figure out how to remedy this situation. I receive the following series of messages when attempting logon. I have attempted to delete the exit, i.e. SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI. This results in: CSV421I MODULE IEFUJI WAS NOT DELETED FROM EXIT IEFUJI. EXIT NOT DEFINED No, create a new SMFPRMxx without any references to IEFUJI and do a T SMF=xx. Then check the other's replies to fix your problem including your SETPROG EXIT. War story: I got many times in such troubles in my sandbox. It helps to have a spare SMFPRMxx and PROGxx members just for that. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN br / br / br / br / ** BMI DISCLAIMER ** This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
If the exit isn't the issue can you alter the logon proc to IKJACCNT. I think it is the starter proc and ispf usually shows that first screen unless the error is happening prior to you getting the ispf panel. John C On Thu, Jun 26, 2014 at 11:29 AM, Jackson, Robin rjacks...@bmi.com wrote: The major problem that I have is I can NOT logon to TSO to make any changes. Thanks, Rob Jackson Mainframe Systems Programming Information Services Group 10 Music Square East, Nashville, TN 37203 (615) 401-2248 (o) (615) 689-1435 (c) email: rjacks...@bmi.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Thursday, June 26, 2014 10:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEFUJI problem, preventing TSO logon Jackson, Robin wrote: I have this situation/condition. I installed an IEFUJI exit and it is preventing logon to TSO, and I can not figure out how to remedy this situation. I receive the following series of messages when attempting logon. I have attempted to delete the exit, i.e. SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI. This results in: CSV421I MODULE IEFUJI WAS NOT DELETED FROM EXIT IEFUJI. EXIT NOT DEFINED No, create a new SMFPRMxx without any references to IEFUJI and do a T SMF=xx. Then check the other's replies to fix your problem including your SETPROG EXIT. War story: I got many times in such troubles in my sandbox. It helps to have a spare SMFPRMxx and PROGxx members just for that. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN br / br / br / br / ** BMI DISCLAIMER ** This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
FTP the offending member to your desktop, correct it and FTP it back. Jim McAlpine On 26 Jun 2014 17:31, Jackson, Robin rjacks...@bmi.com wrote: The major problem that I have is I can NOT logon to TSO to make any changes. Thanks, Rob Jackson Mainframe Systems Programming Information Services Group 10 Music Square East, Nashville, TN 37203 (615) 401-2248 (o) (615) 689-1435 (c) email: rjacks...@bmi.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Thursday, June 26, 2014 10:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEFUJI problem, preventing TSO logon Jackson, Robin wrote: I have this situation/condition. I installed an IEFUJI exit and it is preventing logon to TSO, and I can not figure out how to remedy this situation. I receive the following series of messages when attempting logon. I have attempted to delete the exit, i.e. SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI. This results in: CSV421I MODULE IEFUJI WAS NOT DELETED FROM EXIT IEFUJI. EXIT NOT DEFINED No, create a new SMFPRMxx without any references to IEFUJI and do a T SMF=xx. Then check the other's replies to fix your problem including your SETPROG EXIT. War story: I got many times in such troubles in my sandbox. It helps to have a spare SMFPRMxx and PROGxx members just for that. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN br / br / br / br / ** BMI DISCLAIMER ** This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
Do you have NJE connection to another system that you can logon to? Cook up a totally vanilla logon proc with no data sets. Ship it over and GENER it into SYS1.PROCLIB . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Jackson, Robin rjacks...@bmi.com To: IBM-MAIN@LISTSERV.UA.EDU, Date: 06/26/2014 09:30 AM Subject:Re: IEFUJI problem, preventing TSO logon Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU The major problem that I have is I can NOT logon to TSO to make any changes. Thanks, Rob Jackson Mainframe Systems Programming Information Services Group 10 Music Square East, Nashville, TN 37203 (615) 401-2248 (o) (615) 689-1435 (c) email: rjacks...@bmi.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Thursday, June 26, 2014 10:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEFUJI problem, preventing TSO logon Jackson, Robin wrote: I have this situation/condition. I installed an IEFUJI exit and it is preventing logon to TSO, and I can not figure out how to remedy this situation. I receive the following series of messages when attempting logon. I have attempted to delete the exit, i.e. SETPROG EXIT,DELETE,EXITNAME=IEFUJI,MODNAME=IEFUJI. This results in: CSV421I MODULE IEFUJI WAS NOT DELETED FROM EXIT IEFUJI. EXIT NOT DEFINED No, create a new SMFPRMxx without any references to IEFUJI and do a T SMF=xx. Then check the other's replies to fix your problem including your SETPROG EXIT. War story: I got many times in such troubles in my sandbox. It helps to have a spare SMFPRMxx and PROGxx members just for that. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
On Thu, Jun 26, 2014 at 11:29 AM, Jackson, Robin rjacks...@bmi.com wrote: The major problem that I have is I can NOT logon to TSO to make any changes. Thanks, Rob Jackson Mainframe Systems Programming You _do_ have a problem. You'll need some sort of alternative access. I don't know how your shop is set up. At my shop, in order of preference, I would use: (1) ssh to get a UNIX shell; (2) line-mode telnet to get a UNIX shell (not TN3270); or (3) ftp. I am assuming that your problem most likely is due to the TSO logon proc being messed up. Most shops have the original IBM TSO proc, called IKJACCNT, set up in the proclib. After all, it is distributed by IBM. If you already have permission (TSOPROC class in RACF) to use this, then on the original TSO logon screen, use the IKJACCNT in the Procedure field on the screen. The problem is that you don't have access to ISPF easily. However, you can get it if you do all the ALLOCATE commands needed by hand. What you can do with this is use SDSF to, hopefully, look at the JCL error in the SPOOL. If your TSO logon JCL is automatically flushed (like many do), you can use SDSF to enter the command: $TJOBCLASS(TSU),OUTDISP=(HOLD,HOLD). But you must now logon to TSO using the failing PROC name. Let it fail. Now log on using IKJACCNT again. Use SDSF from the READY prompt and look at the JCL. At this point, hopefully you can see what you need to fix. Use ftp on your desktop to download the PROC to your desktop. Use some editor such as Notepad++ (a nice one on Windows) or (vim|emacs) on Linux. Fix the JCL. Use ftp to upload it back to z/OS. Logon to TSO using the PROC. If you have the IKJACCNT procedure on your system, but _you_ don't have access to it, use ftp to run a job as a SPECIAL user (RACF sec admin) similar to: //RACFWORK JOB //RACF EXEC PGM=IKJEFT01 //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * RDEFINE TSOPROC IKJACCNT UACC(NONE) PE IKJACCNT CLASS(TSOPROC) ACCESS(READ) ID(myracfid) /* // The above must be run by a SPECIAL user. There are other methods which I personally would use. Except for the fact that, in my case, I have access to multiple different TSO logon procs, all of which have access to ISPF. Which is my easy way to do things. If the problem is not the TSO logon procedure having a JCL error, then you will likely need to use ftp from your desktop to run jobs to try to fix your problem. I assume the job in question is in the file job.jcl. You submit this via ftp like: ftp zos user password quote site filetype=jes put job.jcl ls get j?? job-output.txt quit Note that when you do the put above, ftp will tell you the job number of the job submitted. Make sure, for ease, that this job has a name which is your RACF id plus a _single_ character. This allows ftp in level 1 to read its output. The ls shows you the status of the job. Oh, make sure the output is in a HELD class, like you probably do for TSO. Once the job is complete, you can retrieve the output using the get command, replacing the question marks with the job number. Hope this was of some use. I have even more esoteric methods that I use. But I'm a z/OS UNIX shell prompt user. And I have installed the entire Co:Z product line from Dovetailed Technologies. So I can basically submit jobs, retrieve their output, and issue z/OS operator commands from a UNIX shell with little difficulty. I don't know how many shops has embraced z/OS UNIX as deeply as I have. -- There is nothing more pleasant than traveling and meeting new people! Genghis Khan Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
Skip Robinson wrote: Do you have NJE connection to another system that you can logon to? Cook up a totally vanilla logon proc with no data sets. Ship it over and GENER it into SYS1.PROCLIB This is a great suggestion. Although I know most people do have one already, *everybody* should have a TSO-only logon proc with *no* data sets allocated in it. Also, everyone should have a rudimentary understanding of TSO EDIT and OUTPUT commands and subcommands. You don't need or want to be a pro (who'd want to be really proficient in TSO EDIT and OUTPUT when ISPF and SDSF are there?). Just play with them enough that you know how to list, edit, and save a data set or member; and to display job output. Then, when events like this one occur, you can: - Log on when the regular proc doesn't work - Edit the logon proc member - Change it to submit it as a batch job, save it with a new member name, and submit the job - See what happened (missing data set is the usual problem but there can be others) - Fix the problem (for example, allocate or catalog the data set, edit the proc to point to the right one) To expand on this a bit more, consider at least one UADS-only recovery user ID, to be used only when the external security manager (e.g., RACF) must be recovered in some fashion to work. Consider what would happen if your backup security database were corrupted and, before you discovered it or could fix it, you lost the primary. Being able to log on to recover would be a most convenient thing were that to happen. (You can trust me that the opposite is a most inconvenient thing.) Recovery when only one system is available is harder. But thinking about how to do it in advance and planting recovery seeds here and there--things like TSO-only logon procs--will save you gobs of time if you ever have to do it. In the meantime, that same NJE connection, if the OP has one, could be used to retrieve a copy of the proc, submit it as a job, retrieve the output, list catalog entries, etc., or even (rename and) replace the proc if necessary with an updated copy. -- John Eells z/OS Technical Marketing IBM Poughkeepsie ee...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEFUJI problem, preventing TSO logon
In 6bf3f0ce0d23c7488dd8418a8c7a4262ec7...@n2mailboxp04.bmi.org, on 06/26/2014 at 04:29 PM, Jackson, Robin rjacks...@bmi.com said: The major problem that I have is I can NOT logon to TSO to make any changes. TELNET to OMVS, or FTP a batch job. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
