|
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@xxxxxxxxxxxx > 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. > >
As an Amazon Associate we earn from qualifying purchases.
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.