Cannot start up TSO

[FILLAH]

Hi there,

We have a problem. We can not start up TSO because JCL ERROR.
How to update the JCL while TSO not ready.
Thank,
Fillah

[Robert Sample]

Is there not another LPAR with TSO running?

[FILLAH]

No, there is not another LPAR with TSO running.

[enrico-sorichetti]

assuming that the NO reply holds.

I just looked at Your profile and Your skill set reports IMS/VS APPLICATION PRAGRAMMER
so You should have no involvement in system support
is that true ( the NO Rreply ) for everybody or just for You ?
if the problem is just Yours ... did You contact Your system support for a solution

otherwise
pretty unbelievable
that nobody is allowed to logon with a different LOGON procedure

if that is the case Your system people have a very hard task at hand

time to implement the first stage of the disaster recovery plan,
to restore a working copy of the system

or consider the ZZSA standalone editor

http://www.cbttape.org/~jjaeger

ask somebody to create an iplable tape for it
or try to create Yourself an IPLable CDrom image
and use it to fix the logon procedure

just curious...
what do the people in the system support group do in their time ?

[FILLAH]

Thank you very much, I have forwarded to my manager.

[enrico-sorichetti]

add on

or try to create Yourself an IPLable CDrom image

the CDROM iso can be downloaded from the link I posted

[enrico-sorichetti]

Is there not another LPAR with TSO running?

Yes, we haven't. Thank.

something is rotten in the state of Denmark

( the No, we haven't. reply was deleted )
seems that we are wasting our time here

[BillyBoyo]

Get the dust of the card-reader, punch the required JCL, and start TSO from there through the console.

More realistically, FTP the TSO-startup member out, edit it it to correct it, outside the Mainframe. FTP it back to where it came from. Start TSO.

Single-volume IPL.

[BillyBoyo]

Is there not another LPAR with TSO running?

Yes, we haven't. Thank.

something is rotten in the state of Denmark

( the No, we haven't. reply was deleted )
seems that we are wasting our time here

That was me, too quick on the trigger thinking the posts were duplicate

[Robert Sample]

FILLAH, I think your post is missing information. Are you saying that when you IPL your system, the TSO started task is failing with a JCL error, or are you saying that when someone attempts to log onto TSO they get a JCL error? If the TSO started task is failing with a JCL error, your best bet will be to use FTP from another machine (assuming TCP/IP is running on your mainframe) to transfer SYS1.PROCLIB(TSO) to the other machine, edit it there to fix the JCL error (and hopefully it will be a simple JCL error to fix), and then FTP the JCL back to SYS1.PROCLIB(TSO) so the IPL can complete normally. If TSO is running and someone attempting to log on gets a JCL error, there should be at least one other TSO logon procedure that hopefully will not have a JCL error; use that logon procedure to get into TSO and then fix the erroneous logon procedure. Since each site can put their TSO logon procedures wherever they want, and call them whatever they want, there's not standard way to find what the problem logon procedure is nor where it is located.

Also, if this LPAR has production work running on it, your company's auditors -- quite rightly in my estimation -- should issue an Audit Finding about the single point of failure of having just one LPAR. And another one for the lack of an emergency IPL system (sometimes called a one-pack IPL) just for cases like this. An emergency IPL system brings up the bare minimum (no onlines like CICS or IMS, no databases, no HSM) to allow someone to sign on and fix problems like TSO JCL errors.