On Mar 19, 2016, at 9:25 AM, Paul Gilmartin wrote:
On Fri, 18 Mar 2016 23:28:46 -0500, Ed Gould wrote:
The way I learned to do it was that logon procs did a universal ex
sysproc(logon) and if you had a pds that had the member logon in it
o Isn't the argument to EX a DDNAME, not a DSNAME?
o What causes that PDS to be allocated? That was the OP's
question.
THE LOGON PROC *OR* execution of an exec on the execution (exec
pgm=ikjeft01 or the session manager name) statement with a standard
logon proc.
Or is the assumption that there's an optional
'prefix.SYSPROC(LOGON)'
and that failure of the EXEC command is tolerable.
it would exec that clist and in that clist you could allocate the
libraries to your liking. With the understanding that if didn't have
IBM libraries first don't come trouble shooting to us.
On Fri, 18 Mar 2016 23:30:27 -0500, Ed Gould wrote:
Don't blame MVS. *YOU* can set it up to your own local standards.
Tunnel vision. That's fine if the "*YOU*" involved is the arbiter of
those "local standards"; not so much for a lowly end user applications
programmer with no authority to modify a logon procedure.
It is semi local standard *IF* the local choose to use it. It is
documented in several TSO manuals.
But on experiment I believe the COMMAND field meets the OP's
needs:
o It's controlled by the end user.
Both.. if the installation wants it that way.
o It persists from session to session.
It does if you use the logon proc to exec a clist.
-- gil
----------------------------------------------------------------------
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
