From: Kurt Goolsbee <K.email@example.com> DCL DD UFCB CHAR(214) BDRY(16); DCL SPCPTR .ODP DEF(UFCB) POS( 1); Is the UFCB properly initialized? The way I interpret the S/38 Data Area manual is that the ODP and the NEXT-UFCB pointers should be initialized to NULL. Can you rely on these being set to NULL the first time a program is called? ====> you do not need to initialize these. Try to initialize as follows: CPYBREP UFCB(1:64), "*"; and you'll see that it still works. The S/38 Data Areas manual also indicates that FLAGS-2 should be X'30' to indicate that we want to be open for reading and writing. Is this necessary? Other examples ( Leif's book @ http://iseries400.org <http://iseries400.org> ) initialize this byte to X'00'. ===> you can set it to x'30'. It doesn't matter, as the real operation is given in the data management option list. Try to set it to x'30' and see if the problem disappears. I don't think it does, but you know me (I'm often wrong, but never in doubt). ====>that entry 60 in the SEPT is overwritten is a severe bug. Your screen handler cannot do this. It must be OS/400 that lets you down. Is it version dependent? +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.