> Is there a difference between sessions and jobs
> in the scope of session variables set by a command file?

No, all CI variables are scoped as job and session global variables.
This means that any process in a given job or a given session has
access to all variables in that job or session.  If a logon UDC or a
script sets a variable and exits the variable still exists. However, the
variables in one job can generally not be accessed in another, and in no
circumstance  can one job/session change the value of another job/session's
variables.

> I have a command file which upon execution sets a session
> variable.  If I run the command in a session I can reference
> the variable but not so in a job.
>
> Example using SHOWACC command file:
>
> in a session...
> :FILE SACMSGF;REC=-100,,F,ASCII
> :ECHO HPDATEF HPTIMEF > *SACMSGF
        ^^      ^^
You need to use !HPDATEF and !HPTIMEF here if you want their value and
not just their name.

> :ECHO These were accessing primary databases >> *SACMSGF
> :CONTINUE
> :SHOWACC FINDB >> *SACMSGF
> :SHOWVAR SHOW@
> SHOWACC = 349
>
> in a job...
> 48 :FILE SACMSGF;REC=-100,,F,ASCII
> 49 :ECHO !HPDATEF !HPTIMEF > *SACMSGF
> 50 :ECHO These were accessing primary databases >> *SACMSGF
> 51 :CONTINUE
> 52 :SHOWACC FINDB >> *SACMSGF
> 53 :SHOWVAR SHOW@
> 54         ^
> 55 No match found for this variable set. (CIWARN 8116)

Does SHOWACC behave differently in a job??  I don't have enough
info here to hazard a guess.

Sorry,
Jeff Vance, CSY