¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: MVS TK4 or CE


 

OK, that's just weird. I'd have?to look at the exit code to be sure, but my guess is that it's scanning for parameters after 'JOB ' and finding the end of the last parameter as the place to insert a comma so it can insert the USER= and PASSWORD= parameters on a new card without worrying about running past column 72.
My standard JOB card is

//MYNRJRA? JOB (5161A020,1A11),'xxxxxxx MAYNARD',CLASS=x,MSGCLASS=X,
//? ? ? ? ? ? ? ? ? ? ? ? ? ?MSGLEVEL=(1,1),NOTIFY=MYNRJR

...so I would never have noticed this problem. (The userID and account field are what I used in my first systems programming job many years ago, so they're a nod to those days.)

On Fri, Oct 28, 2022 at 1:55 PM Patrik Schindler <poc@...> wrote:
Hello Bob,

Am 28.10.2022 um 15:35 schrieb Bob Polmanter <wably@...>:

> Well, if you have the TSO submit exit properly installed (already part of TK4-), it will automatically insert userid and password on the job card if you have not already coded those parameters.

As said not in all cases. At least for stock TK4-.

If your first job card just says:

//MYJCL? ? ? ? JOB

substitution will not happen. At least that's what I've discovered. Can't find the thread anymore, though. But I've just now verified the issue to refresh my memory.

Sysout:

1? ? ?//POCCRTPG? ? ?JOB? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? JOB 9990
2? ? ?//COBUCL? ? ? ?EXEC COBUCL? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 00000200
°Ú¡­±Õ
RAKF0005 INVALID ATTEMPT TO ACCESS RESOURCE
RAKF000A? PROD? ? ,POCCRTPG,DATASET ,POC.SSTATS.LOADLIB

Because substitution isn't taking place.

Compare sysout to when I just add a MSGCLASS statement in the original JCL:

1? ? ?//POCCRTPG? ? ?JOB? MSGCLASS=A,? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?JOB 9992
? ? ? //? ? ? ? ? ? USER=POC,PASSWORD=? ? ? ? ? ? ?GENERATED BY GDL
2? ? ?//COBUCL? ? ? ?EXEC COBUCL? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 00000200

All steps pass through without issue, because the job is run with my user and thus has RAKF access to the loadlib granted.

Maybe try yourself to understand?

I've dug through contemporary manuals to find evidence that an "empty" job card with just the job's name is *valid* but apparently "GDL" fails to find the right spot to insert user/password when the card has no extra parameters?

> If you code them, then the submit exit won't alter what you coded and you are on your own for that job.

This is what I would expect to happen.

:wq! PoC










--
Jay Maynard

Join [email protected] to automatically receive all group messages.