I liked having DD's in my proc, but I had a second one with no DD's like
you recommend. That saved the embarrassment of having to wander over to
another sysprog's desk with my head held low.
On 3/6/2020 10:20 AM, Steve Smith wrote:
IMHO, a TSO logon proc should have no (0, zero, none, nada,
It' s not my dog.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Steve Smith
Sent: Friday, March 6, 2020 1:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL error during TSO/E logon
IMHO
z3
> > >
> > >
> > > ____________________
> > > From: IBM Mainframe Discussion List on
> behalf
> > > of ITschak Mugzach
> > > Sent: Friday, March 6, 2020 6:07 AM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > >
_
> > From: IBM Mainframe Discussion List on behalf
> > of ITschak Mugzach
> > Sent: Friday, March 6, 2020 6:07 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: JCL error during TSO/E logon
> >
> > You can used recycled paper as well... I thought no
Discussion List On Behalf Of
ITschak Mugzach
Sent: Friday, March 6, 2020 6:32 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: JCL error during TSO/E logon
CAUTION EXTERNAL EMAIL
Shmuel,
I did mentioned the need to have an allocation free TMP procedure. However, if
the OP can't login
/mason.gmu.edu/~smetz3
>
>
>
> From: IBM Mainframe Discussion List on behalf
> of ITschak Mugzach
> Sent: Friday, March 6, 2020 6:07 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JCL error during TSO/E logon
>
> You can used recycled
@LISTSERV.UA.EDU
Subject: Re: JCL error during TSO/E logon
You can used recycled paper as well... I thought no one can login, so you
must use the console to modify stcclass and print to viee.
ITschak
בתאריך יום ו׳, 6 במרץ 2020, 13:05, מאת Seymour J Metz :
> Why kill a tree?
>
>
> --
> Sh
PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JCL error during TSO/E logon
>From the dawn of time, it was deucedly difficult to find the cause of a JCL
error during TSO logon. Then several releases ago, we were treated to a
'fix'. The error would be displayed on the user's screen, allowing the
prob
on.gmu.edu/~smetz3
>
>
>
> From: IBM Mainframe Discussion List on behalf
> of ITschak Mugzach
> Sent: Friday, March 6, 2020 1:21 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JCL error during TSO/E logon
>
> Modify tso class in j
Why kill a tree?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
ITschak Mugzach
Sent: Friday, March 6, 2020 1:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL error during TSO/E logon
Modify tso class in jess to keep the joblog. Your operators can print it
for you to review the error
ITschak
בתאריך יום ו׳, 6 במרץ 2020, 1:08, מאת Jesse 1 Robinson <
jesse1.robin...@sce.com>:
> From the dawn of time, it was deucedly difficult to find the cause of a
> JCL error during TSO
Back in Ye Olde Days I had such a problem (very annoying when users would call
the support desk about these things).
We had a modified IKJEFLD that allowed overrides of PROCs and accounts without
requiring UADS entries.
What I did would call the accounting system to verify that the account was
On Thu, 5 Mar 2020 21:07:32 -0500, Tom Conley wrote:
>
>..., I've used the following JCL
>for years to check out procs that fail (typically my STC sysout goes to
>the bit bucket):
>
>//IBMUSERC JOB 'IBMUSER',
>// CLASS=A,
>// NOTIFY=,
>//
On 3/5/2020 6:08 PM, Jesse 1 Robinson wrote:
From the dawn of time, it was deucedly difficult to find the cause of a JCL
error during TSO logon. Then several releases ago, we were treated to a 'fix'.
The error would be displayed on the user's screen, allowing the problem to be
corrected
is set up for.
Not sure this is a TPX issue. But more likely the TSOPROC process in SAF.
Lizette
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Jesse 1 Robinson
Sent: Thursday, March 5, 2020 4:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JCL error during TSO/E logon
>From the dawn of time, it was deucedly difficult to find the cause of a JCL
>error during TSO logon. Then several releases ago, we were treated to a 'fix'.
>The error would be displayed on the user's screen, allowing the problem to be
>corrected within seconds. Yesterday we had such a
16 matches
Mail list logo
