× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Title: Option in PDM for starting up code/400
Chris,
Here are the 3 PDM options that I use:
 
CB:
CALL QCODE/EVFCFDBK PARM('37' 'Y' 'OS400' '<LOCAL> CODEBRWS "<>&L/&F&N)"')
 
CD:
CALL QCODE/EVFCFDBK PARM('37' 'Y' 'OS400' '<LOCAL> CODEDSU "<>&L/&F&N)"')
 
CE:
CALL QCODE/EVFCFDBK PARM('37' 'Y' 'OS400' '<LOCAL> CODEEDIT "<>&L/&F(&N)"')
 
The third parm needs to be the name of your Code/400 server.  Also note &L not &I.
 
Barry Hoffman
National Seminars
-----Original Message-----
From: Chris Proctor [mailto:cproctor@gartsports.com]
Sent: Tuesday, April 24, 2001 1:03 PM
To: CODE400-L (E-mail)
Subject: Option in PDM for starting up code/400

Hi all,

I'm a newbie to code/400, but I read an email yesterday about setting up an option to start code/400 from PDM.  The email said to set up the option like this:

call qcode/evfcfdbk parm('37' 'Y' 'PCTCI' '<LOCAL> CODEEDIT "<> &l/&F(&N)" /M Y /N')

So, all excited (it doesn't take much!) I tried it and it didn't work!  :-(   In fact it didn't do anything at all.....no error message, NOTHING! This is the first time we've ever tried this, so I'm not even sure the AS/400 is setup properly (if anything has to be configured on it).  Can someone possibly point me in the right direction?

Thanks,

Chris Proctor
Manager of Systems Integration
MIS

<<...OLE_Obj...>>
1060 Broadway
Denver, CO 80203

Phone (303) 863-2280
Fax     (303) 863-2263
mailto: cproctor@gartsports.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.