SYSTSIN and SYSTSPRT "Missing"

[Ken Hynes]

Hello,

I am working on a system with some very "Old" LOGON PROCS. In reviewing
the JCL I noted that none of the PROC's have SYSTSIN or SYSTSPRT in them
and assume that ISPF (or TSO) must be taking care of it as a default. Is there
any advantage or disadvantage in adding the two statements while I'm
cleaning up the PROC's?

//SYSTSPRT DD TERM=TS,SYSOUT=*
//SYSTSIN DD TERM=TS

Thanks.....Ken Hynes

[Paul Gilmartin]

Aren't these normally used only by IKJEFTnn in batch, not
by terminal sessions?

Are TERM and SYSOUT not mutually exclusive?

-- gil

[John P Kalinich]

Ken Hynes of the ISPF discussion list <ISP...@LISTSERV.ND.EDU> wrote on
12/04/2008 01:24:04 PM:

I think these are required for TSO execution in batch. So, if you are
executing your logon procedure in batch, I would include them.

Regards,
John K

[Paul Gilmartin]

On Dec 4, 2008, at 12:45, John P Kalinich wrote:
>>
>> //SYSTSPRT DD TERM=TS,SYSOUT=*
>> //SYSTSIN DD TERM=TS
>
> I think these are required for TSO execution in batch. So, if you are
> executing your logon procedure in batch, I would include them.
>

Does "DD TERM=..." work in batch?

-- gil

[John P Kalinich]

Paul Gilmartin of the ISPF discussion list <ISP...@LISTSERV.ND.EDU> wrote
on 12/04/2008 02:20:35 PM:

Yes.

[John P Kalinich]

Paul Gilmartin of the ISPF discussion list <ISP...@LISTSERV.ND.EDU> wrote
on 12/04/2008 02:20:35 PM:

> On Dec 4, 2008, at 12:45, John P Kalinich wrote:

After looking at my batch TSO JCL, I do override SYSTSPRT and SYSTSIN with
SYSOUT=* and DD * respectively. Sorry.

Regards,
John K

[Paul Gilmartin]

On Dec 4, 2008, at 16:58, John P Kalinich wrote:
>>>
>>> I think these are required for TSO execution in batch. So, if
>>> you are
>>> executing your logon procedure in batch, I would include them.
>>>
>> Does "DD TERM=..." work in batch?
>>
>
> After looking at my batch TSO JCL, I do override SYSTSPRT and
> SYSTSIN with
> SYSOUT=* and DD * respectively. Sorry.
>

The example in:

Linkname: Writing a logon procedure, 3.2.3.2
URL: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/
BOOKS/ikj4b490/3.2.3.2

says:

3.2.3.2 "z/OS V1R10.0 TSO/E Customization"

//AFPROC EXEC PGM=IKJEFT01,DYNAMNBR=20
//SYSUT1 DD DSN=&SYSUT1,UNIT=SYSDA,SPACE=(1700,(400,50))
//SYSUT2 DD DSN=&SYSUT2,UNIT=SYSDA,SPACE=(1700,(400,50))
//SYSUT3 DD DSN=&SYSUT3,UNIT=SYSDA,SPACE=(1700,(400,50))
//SYSPROC DD DSN=CLIST.PROC.LIB,DISP=SHR
//SYSLIB DD DSN=SYS1.MACLIB,DISP=SHR
//SYSIN DD TERM=TS
//SYSPRINT DD TERM=TS

________________________________________________________________________
___________________

Figure 8. Sample logon procedure

The only statement you must include in a logon procedure is an
EXEC statement that
identifies the TMP. ...

I assume SYSIN, SYSPRINT, SYSTSIN, SYSTSPRT, ... are there at the
whim of the customizer. SYSPROC (why not SYSEXEC?) seems more
relevant.

-- gil

[Mark Zelden]

On Thu, 4 Dec 2008 17:23:04 -0700, Paul Gilmartin <PaulGB...@AIM.COM> wrote:

>
> SYSPROC (why not SYSEXEC?) ...

I'm sure you know this. SYSPROC will work for CLISTs and REXX.
If only SYSEXEC was included, CLISTs would not work. Better
perhaps to have asked "why not SYSPROC and SYSEXEC".

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark....@zurichna.com
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

[Ken Hynes]

Thanks to all for the input.

The concern about the SYSTSIN and SYSTSPRT came as a result of doing a
JCLCHECK/JOBSCAN on a large number of LOGON PROC's being affected by a
software change -- the tool gave a message about these two DD statements
being missing. I have since tested several copies of the PROC's with the
additional statements and they work "fine" -- with or without.

My concern was around any potential issues, plusses or minuses associated
with adding them to TSO sessions as opposed to batch -- I was aware of the
Batch requirements.

Per Mark Zelden's input about SYSPROC and SYSEXEC -- in most cases Both
are included. I did not include full copies of the PROC's involved as there were
a large number of them and I was only focused on the two DD statements as
they related to the online TMP session.

I am working on a system where the PROC's have not been maintained for
some time and have been doing some major cleanup on them as part of
updating a particular software package. I can't decide if this falls into the
category of "No Good Deed Goes Unpunished" or "Fools Rush In...", but
anyway thanks again for the input.

.....Ken Hynes