Re: Preloaded Command Prompts

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 11/09/2018
09:57:13 AM:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 11/09/2018
07:40:21 AM:

We do this by a CPY* command which then calls the ADD* command.
For example, our CPYJOBSCDE command retrieves a current job schedule

entry

and then optionally prompts you for the ADDJOBSCDE.
Copy Job Schedule Entry (CPYJOBSCDE)

Type choices, press Enter.

From job name . . . . . . . . . > ACD0010 Name
Entry number . . . . . . . . . . *FIRST 000001-999999,

*FIRST,

*LAST
To job name . . . . . . . . . . *FROMJOB Name, *FROMJOB
Prompt ADDJOBSCDE? . . . . . . . *NO *YES, *NO

Comments give you a clue where we got the basis from
/* Similar to CRTDUPSCDE from www.midrange.com. */

OK, so you're saying that the only way to accomplish this is

with

separate commands specific to the action to be taken. If I must, then I

must. Thanks.

Related question... Since I have to create separate commands and
all of these commands will have the same basic parameters, is there a way
that I can use the same CPP for all of these commands? Meaning: other
than having a dummy parameter that shows on the command prompt screen, is
there a way for the CPP to know which command was used to invoke it --
such as a hidden parameter with the command action in it?


Sincerely,

Dave Clark