|
This was pretty good. However what happens when you have multiple schedule entries with the same name? For example, we have a job that runs 5 times a day. We want to add a sixth. We have to fill in the ENTRYNBR parameter to get the QCMDCHK prompter to work. Then the ADDJOBSCDE fails because this is not a valid parameter. We would have to modify this program to strip out this parameter. But as Robert said, this was a beautiful technique. rburger@home.net on 07/31/2000 08:43:16 AM Please respond to MIDRANGE-L@midrange.com@Internet To: MIDRANGE-L@midrange.com@Internet cc: Fax to: Subject: Re: Is there a way to copy an existing Job Schedule Entry to a new one? Brendan, Every time I think I'm beconming a pretty competent CL programmer, someone blows me away. What you have proposed is such a simple but powerful way to do what I needed -- I've never even given the remotest consideration to "substituting" one command for another. Beautiful! Thanks for the solution and the lesson that I'm sure will have many other benefits, Robert ----- Original Message ----- From: Brendan Bispham <midrangel@black-and-blue.com> To: <MIDRANGE-L@midrange.com> Sent: Friday, July 28, 2000 7:52 AM Subject: RE: Is there a way to copy an existing Job Schedule Entry to a new one? > The simplest program for occasional copies is possibly this... It prompts > you for an entry name, and after you select one, it puts the parms into a > separate ADDJOBSCDE command. > > PGM > DCL VAR(&CMD) TYPE(*CHAR) LEN(2000) + > VALUE('?CHGJOBSCDE ??JOB() ??CMD() + > ??FRQ() ??SCDDATE() ??SCDTIME() + > ??RELDAYMON() ??SAVE() ??OMITDATE() + > ??RCYACN() ??JOBD() ??JOBQ() ??USER() + > ??MSGQ() ??TEXT()') > CALL PGM(QCMDCHK) PARM(&CMD 2000) > CHGVAR VAR(&CMD) VALUE('?ADDJOBSCDE' *BCAT + > %SST(&CMD 12 1988)) > CALL PGM(QCMDEXC) PARM(&CMD 2000) > ENDPGM > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.