Last time around, I presented the List Job Schedule Entries (LSTJOBSCDE) command, which offers the capability to list all or just a subset of the IBM i job schedule entries (WRKJOBSCDE) to an output file. In addition to the uses discussed in the accompanying article of such an output file, there’s the option of using it to merge, migrate, and copy job schedule entries between systems. On one system, you can create an output file containing the desired selection of job schedule entries and then save and restore that output file to another system. You can then use the output file as input to the new Update Job Schedule Entries (UPDJOBSCDE) command on the system to which the output file was restored.
Job schedule entries that are scheduled for a particular date and time will not be added to the job scheduler if that date and time has passed. All objects referenced by each job schedule entry—such as job queues and job descriptions, as well as commands to run—must exist on the system where this command is run in order for the update to be successful.
A completion message indicating the number of job schedule entries that were added, how many attempts to add a job schedule entry that failed, as well as the number of warnings issued for the added entries is sent once processing of the output file is completed. For details about which job schedule entries were successfully added and which entries failed, please check the job log following the UPDJOBSCDE command execution. Also note that all restrictions applying to the Add Job Schedule Entry (ADDJOBSCDE) command also apply to this command. Please refer to the ADDJOBSCDE command help text for all the details.
As another customization option, you can use interactive SQL or a simple database record editor like IBM’s Database File Utility (DFU) to delete records from the output file before running the UPDJOBSCDE command and thereby exclude the selected entries from being added to the job scheduler on the new system.
Articles on Apis 