Re: Message SubFile

Michael Smith wrote:

The coding error :

DISPLAY-001.
MOVE SPACES TO FLD1 OF FMT1-O.
WRITE DISPLAY-RECORD FORMAT IS "FMT1".
MOVE 'MSGSFLCBL' TO PGMQ OF MSGSFLC-O.
WRITE DISPLAY-RECORD
FORMAT IS "MSGSFLC"
INDICATORS ARE WS-INDICATORS.
READ DISPLAY-FILE
INDICATORS ARE WS-INDICATORS.

Michael:

I'm guessing that the error is the mismatch between 'MSGSFLCBL' and the Identification Division Program-ID, which is 'SFLCBL'. The error can be eliminated by changing either or both so that they match and also making sure that the *MODULE and *PGM are created as the same name used for Program-ID.

As written, the Program-ID becomes the 'procedure name' that is in the call stack -- but only if you compile as ILE. If you compile as ILE, you'll want to ensure that *PGM, *MODULE, procedure and subfile SFLPGMQ names/values are all what you want them to be.

If you compile as OPM COBOL, everything should work as written.

#2 was the result of using
DATA DIVISION.
FILE SECTION.
FD DISPLAY-FILE01 DISPLAY-RECORD.

LABEL RECORDS ARE STANDARD.
01 DISPLAY-RECORD.
COPY DDS-ALL-FORMATS OF FS2CBL.

Thanks to Jerry Thomas for point the following:
COPY DDS-ALL-FORMATS OF FS2CBL

05 fs2cbl-record pic x(??). 05 FMT1-I redefines FS2CBL-RECORD.
05 FMT1-O redefines FS2CBL-RECORD.
06 SCFIELD pic x(10)

So when I moved values to the two fields, one "appeared" to be corrupted.

The resolution was:

always copy my different formats into a different are of working storage and
then reference them on the write. This keeps from overlaying data buffer.
FD SCREEN-FILE LABEL RECORDS ARE OMITTED.
01 SCREEN-RECORD PIC X(999).

WORKING-STORAGE SECTION.

01 DSPFMTA. COPY DD-DSPFMTA-O OF DSPEX05.
01 DSPFMTB. COPY DD-DSPFMTB-I-O OF DSPEX05.

01 DSPFMTC. COPY DD-DSPFMTC-I-O OF DSPEX05.

01 MSGFLC. COPY DD-MSGFLC-I-O OF DSPEX05.

.

WRITE SCREEN-RECORD FROM MSGFLC FORMAT IS "MSGFLC" INDICATORS ARE WS-SCREEN-INDICATORS.
CALL "CLRMSG".
WRITE SCREEN-RECORD FROM DSPFMTC FORMAT IS "DSPFMTC"

Yes, the definitions in the File Section are essentially actual file I/O buffers (or pretty close to them). You can perform data operations there, but it's generally advisable to WRITE FROM and READ INTO separate Working-Storage Section areas.

RPG is well known for moving data elements out of the file buffer areas into variables that are maintained in separate memory. COBOL allows you to choose not to do that, and can make shooting yourself in the foot much easier.

Tom Liotta