|
X'B8' WDMUFLG2 1 byte WDMUMKCP 1 bit bit 0 File Mark Counter 0=QDMCOPEN will set the Invokation mark 1=User must set the invokation mark. WDMUCLMG 1 bit bit 1 "Close Parameters Spefified" If set indicates that QDMCLOSE is to merge the close parameter into the ODP. WDMUBRCD 1 bit bit 2 If set BLKRCD(YES) is specified on the UFCB. Blocked records will be transferred to the users buffer on each IO. WDMUSEPI 1 bit bit 3 If set IO routines will assume that the indicators are in a separate indicator area. WDMUACQA 1 bit bit 4 If set all program devices defined to the file are to be acquired when the fiel is opened. (set to 1 only by CL compiler) WDMUSNGB 1 bit bit 5 If set and the file is open for input and output then the FM is to use a single buffer for both input and output. Unused 2 bits bit 6-7 -----Original Message----- From: Leif Svalgaard [SMTP:leif@leif.org] Sent: Wednesday, December 06, 2000 4:35 PM To: MI400@midrange.com Subject: Re: Storage Initialization Kurt, I don't have the Data areas book. could you email me the full description of MORE-FLAGS? ----- Original Message ----- From: Kurt Goolsbee <K.goolsbee@pentasafe.com> To: <MI400@midrange.com> Sent: Wednesday, December 06, 2000 4:05 PM Subject: RE: Storage Initialization > What we have set for MORE-FLAGS is X'04' which means to use the same buffer > for both input and output. > > -----Original Message----- > From: Gene_Gaunt/ReviewWorks@reviewworks.com > [SMTP:Gene_Gaunt/ReviewWorks@reviewworks.com] > Sent: Wednesday, December 06, 2000 3:35 PM > To: MI400@midrange.com > Subject: RE: Storage Initialization > > > > Extrapolate this thought: > > MORE-FLAGS value X'10' means use the 'seperate indicator area' > pointer at > POS(H'61'). > MORE-FLAGS value X'80' means use the 'acquire program device control > block' > pointer at POS(H'71'). > MORE-FLAGS value X'40' means use the 'next UFCB' pointer at > POS(H'51')? > > Maybe MORE-FLAGS value X'00' instead of X'40' will fix the problem. > > > +--- > | 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 > +--- +--- | 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 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.