Re: User-Defined Options for PDM?

Here is the help topic from WDSCi Help (Search "PDM user defined options")

Matt

CODE Tips and Techniques

Invoke CODE Tools From an iSeries PDM Session
You can create Programming Development Manager (PDM) user-defined options 
to start the CODE tools from a list of members or programs. You can invoke 
the CODE editor from an iSeries session. 
Here is an example of a user-defined option to invoke the code editor from 
a list members using substitution variables. 
CALL QDEVTOOLS/EVFCFDBK PARM('37' 'Y' 'OS400'
 '<LOCAL> CODEEDIT "<server>lib/file(member)"')

Note: 
Any of the command-line options for CODEEDIT can be included in the 
CODEEDIT string. Refer to the command-line syntax (type CODEEDIT /H from a 
workstation command line) for more information on CODEEDIT parameters. 
It is also possible to use the CODEBRWS command to invoke the editor and 
browse a member without allowing changes to be made: 
CALL QDEVTOOLS/EVFCFDBK PARM( '37' 'Y' 'OS400' '<LOCAL> CODEBRWS
                "<server>lib/file(member)"' )

It is also possible to create user-defined options through Programming 
Development Manager (PDM), Application Development Manager (ADM), and 
Application Dictionary Services (ADS). 
Here is an example of a user-defined option to invoke the CODE editor from 
a list of members: 
                     Change User-Defined Option
 
Type changes, press Enter.
 
 Option  . . . . . . . . .   CE   Value to change to
 
 Command . . . . . . . . .
 CALL QDEVTOOLS/EVFCFDBK PARM('37' 'Y' 'OS400'
      '<LOCAL> CODEEDIT "<>&L/&F(&N)"')

Here is an example of a user-defined option to invoke the CODE editor on a 
list of ADM parts: 
                     Change User-Defined Option
 
Type changes, press Enter.
 
 Option  . . . . . . . . .   CA   Value to change to
 
 Command . . . . . . . . .
 CALL QDEVTOOLS/EVFCFDBK PARM('37' 'Y' 'OS400'
      '<LOCAL> CODEEDIT "</ADM>&ZP/&ZL/&ZT/&ZN"')

User-defined options can also be created to use the CODEBRWS command. 
IMPORTANT NOTES: 
In order to call the QDEVTOOLS/EVFCFDBK command, the library containing 
the EVFCICFF communications file must be found in the library list of your 
interactive job. The EVFCICFF file only applies to APPC communication. 
If the CODE editor is to be invoked for an OS/400 member or program, then 
the STRCODE command must first be run from another OS/400 session in order 
to establish the required communications. The library list of the session 
running STRCODE is the library list used by the CODE editor. 
The first three parameters of the QDEVTOOLS/EVFCFDBK command (the '37', 
'Y', and 'OS400') are for program use only. They should not be altered. 
The empty brackets <> shown in the examples here tell the various CODE 
commands to simply use the first CODE active server it can find. You may 
instead choose to hard-code a specific server name, such as <OS400>. 
To improve the start-up performance of subsequent editor sessions, leave 
an empty CODE editor window running on your PC. 





CProctor@xxxxxxxxxxxxxxxxxx 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
08/18/2005 11:03 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: [WDSCI-L] User-Defined Options for PDM?






Thanks, Matt. Do also have the ones for DSPF and PRTF?

Chris Proctor
TransMontaigne, Inc.
Energy Services - IT
303.860.5192 (Direct)