× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Storage Initialization
  • From: Kurt Goolsbee <K.goolsbee@xxxxxxxxxxxxx>
  • Date: Wed, 6 Dec 2000 14:58:24 -0600

It is QDMCOPEN that is letting me down.  All it has to go on is the UFCB
that gets passed to it.  What would happen if the NEXT-UFCB was pointing to
a real pointer (not another UFCB to open).  Is QDMCOPEN going to know that
it isn't another UFCB?    

        -----Original Message-----
        From:   Leif Svalgaard [SMTP:leif@leif.org]
        Sent:   Wednesday, December 06, 2000 2:01 PM
        To:     MI400@midrange.com
        Subject:        Re: Storage Initialization

        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 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.