IBM Mainframe Forum Index
Log In
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register

JCL Dynamic System Symbols

IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message

Senior Member

Joined: 29 Apr 2008
Posts: 1776

PostPosted: Fri May 26, 2023 8:53 pm
Reply with quote

The manual says:
The name of the job. Shown in 1-8 characters. In the special case when the job name is *MASTER*, &JOBNAME resolves to #MASTER# to avoid the error of using the asterisk as part of a data set name.
Under z/OSĀ®, it is valid to define a user ID that is all numeric. Under z/OS UNIX, this all-numeric user ID might be propagated as a job name in the case of a fork() or non-local spawn(); this can lead to allocation failures when &JOBNAME is used in substitution for a data set name.

If you specify the &JOBNAME dynamic system symbol in a START command for a started task, the resolved substitution text for &JOBNAME is the name of the job assigned to the address space that calls the symbolic substitution service, not the address space of the started task.

But when used with regular JCL submit from ISPF, the result is not the name from the JOB statement, but always as if it was set:

Any idea?
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM


Similar Topics
Topic Forum Replies
No new posts Insert system time/date (timestamp) u... DFSORT/ICETOOL 5
No new posts Synctool-dynamic split job for varyin... JCL & VSAM 7
No new posts the system or user abend SF0F R=NULL COBOL Programming 0
No new posts We are looking for DB2 system adminis... Mainframe Jobs 0
No new posts Dynamic file allocation using JCL JCL & VSAM 8
Search our Forums:

Back to Top