Re: Command Processing -- MIDRANGE-L

>It isn't clear exactly what you're having trouble with. 
>(But I'm not sure you're going in the right direction 
>from the beginning.) It seems you know well enough 
>about creating PDM options and you have created 
>a customized "Create Object" function which works.

Thank you all.  QCMDCHK works as many of you have pointed out.  So to clear up 
any confusion here's the solution:

1. Created a command with parameters: source library, source file, source 
member and source type. 
2. Added that to the PDM options using F16 from PDM.  
3. The command parameters were filled in with the replacement characters &L, 
&F, &N and &T.
4. The command calls a CL which behaves differently for each Type of source 
passed to it.  In the CL I build the command string (&CMD is the variable that 
I use)  using CHGVAR with a lot of *CAT and *TCAT's and since I want to prompt 
the command I place a question mark in front of the command which causes the 
prompt.  I use a couple of other selective prompting prefixes like '?<' and 
then call QCMDCHK (2 parms, the command and it's length)  which prompts the 
command, accepts changes and passes those changes back to my variable (&CMD).
5. I then take that result and process the command using SBMJOB with the 
checked parameter (&CMD) as the RQSDTA value or I run it interactively using 
QCMDEXC.  
6. Compiled the CL and then tested the results which work fine.
7. Externalize the lookup for the defaults for the command with a file and 
incorporate that lookup routine into the CL.  (this lets us change the defaults 
for any individual or group of individuals on the system by changing 1 file.)

Here're the problems solved:

PDM has 1 option to create a program and another to create a module.  Both 
create an object based on the type source member selected, in addition, option 
14 will create an object for any number of source file types.  We want to 
create an option that will do the same thing but provide 2 additional features:
1. If the source is *LE, prompt what it is you want to create using a pop-up 
window.  For example:  CRTBNDCL or CRTCLMOD or CRTPGM.  Once you make your 
selection the correct command is prompted with the source and library names 
filled in.
2. Since there are different development environments that can not all have the 
same default parameters for their create commands when a create is requested 
display the command using the desired defaults based on the user profile but 
permit changes to most of the parameters at all times.

Problems solved.  
I probably should have thought about QCMDCHK, I'm glad you folks did.  Thank 
you for your help, this is working very well.

Bill




+---
| 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
+---