Re: transfer of s36(externally describe)

keith.nolan@dubport.ccs.ie wrote:
> 
> How do we externally describe a system36 file??  Probably a stupid question I 
>know.....

Keith:

The S/36 programs don't know or care if the files are externally 
described, so this is a very normal way to start a "conversion".
It will be mandatory in order to use RPGIII or RPGIV, so why not
go ahead with this piece of the puzzle.

 The S/36 files are easy to convert IF you have a "complete" layout:

          BACKUP ALL FILES BEFORE USING THIS METHOD.

1. Create a Test library
2. Create DDS specs for S/36 file & compile new file
3. copy S/36 file from QS36F to testlib/newfile with *nochk option
4. CHECK the file VERY closely for correct field definitions....
5. After a very complete check, run a few programs against new file.
6. If tests all run ok.. copy "new" file to QS36F and move on to next
file.

Notes:

You MUST account for every single byte in old file including blanks.

Make sure you define all packed and signed numeric fields correctly in
DDS.

Use a user profile that is NOT placed in the S/36EE automatically, so
that the QS36F is NOT in the LIBL. This will prevent accidental 
destruction of production files when you compile "new" file.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---