|
Workstation ID is %WS% or %WSID% in OCL (I think %WS%). Whether or not that helps you is another story. Okay, you are required, damanded, edicted to write this is S36. Okay, but what is to say you can't use modern programming techniques? The only restriction I would see is if you are creating an export file, that is, one you need to send to another computer to import. Otherwise, what is limiting you to creating only one file and using record type selection, and not creating 2 separate files and using matching records? It would still be S36 code. Regards, Jim Langston -----Original Message----- From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On Behalf Of Kmh0421@aol.com Sent: Thursday, September 20, 2001 2:07 PM To: RPG400-L@midrange.com Subject: Fwd: INFDS Sy 36 PSDStr... Issue -- -- [ Picked text/plain from multipart/alternative ] Ok, my real problem is this.... I am NOT a 36 pro.... need help!! As you may remember, I am rewriting old icky stuff , still, into newer old icky stuff per client requirement, demand, edict, etc. Anyway, what I have to do is this: I am creating transactions in a 64 character flat file. Some of the records are Batch Hdr records (i.e. Positions 1-4 are 'B', '1234', etc.etc.) and some are detail records (i.e. Positions 1-16 are 'A', 'TAG123', 'PART123456', xxxx etc etc etc....). I have the last 13 positions of the record to hold whatever I wish. I need to be able to retrieve the records later in the program for 'REVIEW'. On one screen, I need to ROLL through the Header records and allow the user to modify them, on another screen, I need to ROLL through the Detail records for the associated Header record to allow modification of them. The records in the transaction file will be written by different workstations. I am only supposed to show the records written by the workstation the user is using. The program must run in 36 mode, and later will be 'converted' (by a package) to a 400 program. Soooooo, I am thinking I must use my 13 positions to store Batch (4) Batch Start RRN (4) Prev Dtl Rcd RRN (4) and a 1? position WSID. I need to get the RRN of the record - how? the WSID of the record - how? Any help is most GREATLY appreciated. Kathie -- From: Kmh0421@aol.com Full-name: Kmh0421 Date: Thu, 20 Sep 2001 13:10:52 EDT Subject: Fwd: INFDS for System 36....and Program Status Data Structure To: RPG400-L@midrange.com X-Plaintext: Picked text/plain from multipart/alternative -- -- [ Picked text/plain from multipart/alternative ] Does anyone have the structure of the INFDS, and the Program Status Data Structure for the System 36? In particular, I am looking for the workstation, without using CLP program, on the 36..... Thanks again; Kathie -- From: Kmh0421@aol.com Subject: INFDS for System 36 To: rpg400-l@midrange.com Sender: rpg400-l-admin@midrange.com Precedence: bulk Reply-To: rpg400-l@midrange.com Date: Thu, 20 Sep 2001 12:36:42 EDT -- [ Picked text/plain from multipart/alternative ] Hi... I can't get into the bookmanager right now. Does anyone have the positions for the system 36 infds? Thanks Kathie _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-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.