Step 3. Submit the batch job
You will be requested to enter the details to be used by the batch job that will be submitted to load the definitions of the selected files.
|
LS@0001198 LOAD/CREATE OTHER FILES
Submit batch load of files selected . . . . . . . . YES YES, NO Using Job name . . . . . . . . . . . . . . . . . . LS@BULKLOD Job description . . . . . . . . . . . . . . . QUSRSYS/DC@JOBD Job queue . . . . . . . . . . . . . . . . . . *JOBD Output queue . . . . . . . . . . . . . . . . USRSYS/PRT02
Submit batch create of files after load . . . . . YES YES, NO OPTIONS FOR BATCH CREATE Produce file and I/O module source listings . . . . NO YES, NO Ignore decimal error / Strip debug data option . . NO YES YES, NO User program to call at completion . . . . . . . . __________
Fnn=Help Fnn=Prompt Fnn=Messages
|
During this same step, you can make the file(s) operational by entering YES for . This will be cause a batch job to be submitted for each physical file definition that is successfully loaded.
These make operational batch jobs will use the same Job description, Job queue and Output queue that was used for the bulk load job. The Job name will be the file name.
To find out what else happens when a file is made operational, refer to Submitting Job to Make File Definition Operational in the