On Thu, Jun 26, 2014 at 11:29 AM, Jackson, Robin <[email protected]> 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 [email protected] with the message: INFO IBM-MAIN
