× 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.


  • Subject: Re: Code/400 and user defined options
  • From: "Alan Novick" <mida@xxxxxxxxxxxxxxx>
  • Date: Thu, 26 Jul 2001 10:35:43 -0400

Title: Code/400 and user defined options
Chris:
 
I'm new to this stuff and as I was coming in to work this morning I was wondering if it was even possible to do what you are asking, and then here was your message.  I'm on V5.1 and got an error message about invalid characters when I used your command.  After some research, here is what worked for me:
 
CALL PGM(QCODE/EVFCFDBK) PARM('37' 'Y' 'OS400' '<LOCAL> CODEEDIT "<>&L/&F(&N)"')               
 
Hope this helps and thanks for posting that it was possible.                                 
 
Alan Novick
Pressman Toy Corporation
New Brunswick, NJ
 
----- Original Message -----
Sent: Wednesday, July 25, 2001 5:09 PM
Subject: Code/400 and user defined options

Hi all!

I had my PDM session setup with user defined options for codeedit, browse, but now that I've upgraded to V5.1, they don't seem to work.  Here's what they look like:

  CALL QCODE/EVFCFDBK PARM('37' 'Y' 'S30' '<OS400A> CODEBRWS "<>&L/&F(&N)"')
  call qcode/evfcfdbk parm('37' 'Y' 'OS400A' '<> CODEEDIT "<OS400A>&L/&F(&N)"')

What is wrong with them? The command shell is of no use whatsoever. Thanks for the help!

Chris Proctor
Gart Sports
Denver


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.