Re: System/36 command from a CL?

Hi!

I know all you wrote in your last message. But my temporary file needs to be
keyed, I don't need just a flat file because after the RPG/400 execution
that fills my temporary file, my CL launch a S/36 procedure that processes
the file...

I found a way to do what I want with STRS36PRC. There is the solution to my
problem:

STRS36PRC  PRC(BLDFILE) PARM(&BATCH *CAT +
             ',I,RECORDS,1000,256,,T,124,5,DFILE,NODUPKE+
             Y,1000')

My file name is dynamically created using the S/36 work station ID retrieved
with the QEXCVTDV API.

Now all my application works fine. Sometimes it is hard to deal with an
production environment that is a weird mix between S/36 and iseries
applications, with some bits of ILE programs ;-)

Charles



"Jerry Adams" <jerry@xxxxxxxxxxxxxxx> a écrit dans
le message de news:443A9C4A.40300@xxxxxxxxxxxxxxxxxx
Some people believe that an RPG II program cannot read/update an
externally described file.  Even though it must be program described in
RPG II, it can be a "flat" file (BLDFILE) or externally described (DDS
or SQL).  Go ahead and externally describe it.


Plus, it would be a very good idea to convert those RPG/400 programs to
RPG IV.  RPG/400 has not been updated since 1992.  Even if you think you
don't need RPG IV, it's a piece of cake to get used to and does the same
things + more that RPG/400 does.  It's much easier to implement (and
learn) these things gradually than, eventually, have it crammed down
your throat later.  Besides, it's more fun.  And then covert to /free
format; more fun still.


* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx
<mailto:jerry@xxxxxxxxxxxxxxx>



Charles St-Laurent wrote:

>Hi!
>
>The file in question is a temporary file that has to be read into a RPG II
>program after I fill it with my RPG/400 program. There is no need (I think)
>to convert this file to a native iseries file with a DDS because all the
>other programs that uses this file define the data internally... Even my
>RPG/400 program writes in this file with EXCPT...
>
>Charles
>
>
><rob@xxxxxxxxx> a écrit dans le message de
>news:OF0DE659C8.BF47E460-ON8525714C.0057D1DE-8525714C.00589D02-tksaTn4SAz1U
i4FbrNnSJA@xxxxxxxxxxxxxxxx
>
>
>>There are a few utilities to execute SQL from CL available.  You could do
>>a
>>CREATE TABLE CHARLES
>>(MYFIELD CHAR (5 ) NOT NULL WITH DEFAULT,
>> MYDATA CHAR (15 ) NOT NULL WITH DEFAULT,
>> PRIMARY KEY (MYFIELD))
>>However, it's been my experience that people often use "without DDS" when
>>they really mean "an internally described file".  Is that your case?
>>
>>Rob Berendt
>>-- 
>>Group Dekko Services, LLC
>>Dept 01.073
>>PO Box 2000
>>Dock 108
>>6928N 400E
>>Kendallville, IN 46755
>>http://www.dekko.com
>>
>>
>>
>>
>>
>>"Charles St-Laurent" <dringpiece@xxxxxxxxxxx>
>>Sent by: midrange-l-bounces@xxxxxxxxxxxx
>>04/10/2006 11:46 AM
>>Please respond to
>>Midrange Systems Technical Discussion
>>
>>
><midrange-l@xxxxxxxxxxxx>
>
>
>>To
>>midrange-l@xxxxxxxxxxxx
>>cc
>>
>>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
>>
>>
>>
>>-- 
>>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>>list
>>To post a message email:
>>
>>
>MIDRANGE-L@xxxxxxxxxxxx
>
>
>>To subscribe, unsubscribe, or change list options,
>>visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>>or email: MIDRANGE-L-request@xxxxxxxxxxxx
>>Before posting, please take a moment to review the archives
>>at http://archive.midrange.com/midrange-l.
>>
>>
>>-- 
>>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>>
>>
>list
>
>
>>To post a message email:
>>
>>
>MIDRANGE-L@xxxxxxxxxxxx
>
>
>>To subscribe, unsubscribe, or change list options,
>>visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>>or email: MIDRANGE-L-request@xxxxxxxxxxxx
>>Before posting, please take a moment to review the archives
>>at http://archive.midrange.com/midrange-l.
>>
>>
>>
>>
>
>
>
>
>