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



Hi, Charles:

Unfortunately, if you use CRTPF with RCDLEN(nnn),
with no DDS source, you cannot create a keyed file,
as far as I can tell...

Take a peek at this article:
   http://www.itjungle.com/guruo/mgo020802-story02.html

I would just create equivalent DDS, then use CRTPF with the
new DDS member, and you can create an equivalent keyed
physical file.

While you are at it, you may want to consider defining the other
fields in the record and making it an externally described file...?

There are several third-party tools to assist with converting your
entire S/36 apps. to "native" OS/400, such as ASNA's ProStart;
see: http://www.linomasoftware.com/modx/products/prostart

HTH,

Mark S. Waterbury

----- Original Message -----
From: "Charles St-Laurent" <dringpiece@xxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Monday, April 10, 2006 11:46 AM
Subject: System/36 command from a CL?


Hi!

I would like to know if it is possible to execute a System/36 command (for
example BLDFILE) from a CL script. Or, if it not possible, how can I create
a keyed physical file without DDS associated with that new file?

BLDFILE ?L'1,2'?_BATCH,I,RECORDS,1000,256,,T,124,5,DFILE,NODUPKEY,1000
<------------ I want to do the equivalent of this S/36 command in a CL
script (a new file with a unique key at position 124... the length of the
file = 256)...

Thanks in advance for your answers

Charles St-Laurent



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.