Author: dbzTHEdinosauer
Posted: Tue Nov 29, 2016 8:00 pm (GMT 5.5)
since changeman submits jcl that it generates based on interactions with the gui,
of course you can create your own job and submit it.
if you would investigate the subfiles within the job in sdsf or whatever you use,
you can find the jcl that was submitted.
it is not located where the jcl spools, but within the second or third sub.spool file (i forget)-
but the fact that you do not know that, or have found it on your own,
leads me to suggest that you do not do it,
at least until your experience and skills level have greatly improved.
you run the risk of doing damage to the package, or the database.
besids, the reason the gui was bought and paid for
is to insure that all the users submit good jcl,
and possibly more importantly,
authorized actions.
the time you think that you are saving by skiipping the gui,
maybe used up looking for a new job.
_________________
Dick Brenholtz
Programming Languages, SQL and JCL have the tendency to do what you coded,
not necessarily what you wanted.
Posted: Tue Nov 29, 2016 8:00 pm (GMT 5.5)
since changeman submits jcl that it generates based on interactions with the gui,
of course you can create your own job and submit it.
if you would investigate the subfiles within the job in sdsf or whatever you use,
you can find the jcl that was submitted.
it is not located where the jcl spools, but within the second or third sub.spool file (i forget)-
but the fact that you do not know that, or have found it on your own,
leads me to suggest that you do not do it,
at least until your experience and skills level have greatly improved.
you run the risk of doing damage to the package, or the database.
besids, the reason the gui was bought and paid for
is to insure that all the users submit good jcl,
and possibly more importantly,
authorized actions.
the time you think that you are saving by skiipping the gui,
maybe used up looking for a new job.
_________________
Dick Brenholtz
Programming Languages, SQL and JCL have the tendency to do what you coded,
not necessarily what you wanted.