SUBMITTING BATCH JOBS FROM CMS TO MVS
 
     The conversion to ACF2/VM and a change to MVS could affect any
user who submits a batch job to MVS from CMS.
     Previously, you had to include //*LOGONID and//*PASSWORD cards in
the jobstream, and they could be placed anywhere.  Now, if a batch job
is submitted without //*LOGONID and //*PASSWORD cards, the job will
use the userid of userid submitting the job.
     So, if you have the same password and userid on both VM and MVS,
you no longer need to include the //*LOGONID and //*PASSWORD cards in
your MVS batch jobs.
     However, if you do want to (or need to) continue using these
cards, they must be placed between the JOB statement and the first
EXEC statement.  If they're anywhere else in the jobstream, MVS will
not process your job.
     If you submit a batch job without a userid, the job will use the
userid of the CMS userid submitting it.  If your MVS userid is the
same as your VM userid, your job will automatically inherit your VM
userid, and no password will be required because you entered your
password when you logged on.  Just remove the //*LOGONID and
//*PASSWORD cards from your jobs.
     Remember:  only users who need to run batch jobs under MVS
userids different from their VM userids will need to use the
//*LOGONID and //*PASSWORD cards, and these cards must be placed
between the JOB statement and the first EXEC statement.
     It is critical that you use two slashes rather than one in your
LOGONID and PASSWORD cards.  While single slashes will be accepted and
used by ACF2, if your JCL has a syntax errors or cancels for any
reason, the listing will show your password in plain text for everyone
to see.  If this should happen, change your password immediately.
     For more information about these changes, contact Matt Simpson at
257-2228, sysmatt@ukcc.uky.edu, 210 McVey Hall.
 
                                              --  Matt Simpson
 
*********************************************************************