|
Joe, This might be helpful: ================================================================== INPUT-OUTPUT SECTION. FILE-CONTROL. select dspfile assign to workstation-SE802D-si access mode is sequential organization is transaction file status is dsp-status. DATA DIVISION. FILE SECTION. fd dspfile. 01 dsprecd pic x(1920). WORKING-STORAGE SECTION. 01 dspfile-area. copy dds-M3MAP-O of SE802D. 01 indicator-area. copy dds-all-formats-indic of SE802D replacing IN50 by wht-message IN51 by red-message. PROCEDURE DIVISION. *---- Send Screen write dsprecd from M3MAP-O format 'M3MAP' indicators m3map-o-indic end-write. *---- Read screen read dspfile record into M3MAP-O format 'M3MAP' end-read. ================================================================== Replace SE802D with your display file name. Replace M3MAP with your DDS record name. Terry > -----Original Message----- > From: Joe Pluta [mailto:joepluta@PlutaBrothers.com] > Sent: Wednesday, July 24, 2002 2:00 PM > To: cobol400-l@midrange.com > Subject: RE: A little shudder here > > > WICKED MEAN EVIL COBOL. > > <grumble> > > Here's an interesting situation. In RPG I can define a > workstation file but > never open it. This will automagically generate the field > definitions for > all the fields in the display file, and so the program can > continue to work > just fine in batch. > > If, however, I try the same thing in COBOL, I get an MCH3601 > error because > evidently the 01-level items (one for each record format) are > evidently not > initialized unless the workstation file is open. > > Does anybody have a way around this? I even tried making the > display file > DEV(*NONE) and even though I opened the file, I still got > initialization > errors when attempting to access the fields in the display file. > > Joe
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.