• Subject: Re: Storage Initialization
  • From: "Leif Svalgaard" <leif@xxxxxxxx>
  • Date: Wed, 6 Dec 2000 14:01:00 -0600

From: Kurt Goolsbee <K.goolsbee@pentasafe.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: dr2@cssas400.com
+---

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].