How to change the *CRTBNDRPG message format by adding two spaces in between the CRT* command and PGM keyword while generating the z* directives?
What we are trying to do, is to adjust the space in between the CRT* command and keyword PGM/MODULE. For example, our Y2U1022 currently has this command:
CRTBNDRPG PGM(&2/&1) SRCFILE(&3/QRPGSRC) DFTACTGRP(*NO) DBGVIEW(*SOURCE) CVTOPT(*DATETIME) OPTIMIZE(*BASIC) USRPRF(*OWNER)
We're trying to put extra space in between CRTBNDRPG and PGM, so it should look like this:
CRTBNDRPG PGM(&2/&1) SRCFILE(&3/QRPGSRC) DFTACTGRP(*NO) DBGVIEW(*SOURCE) CVTOPT(*DATETIME) OPTIMIZE(*BASIC) USRPRF(*OWNER)
(notice the double spaces in between CRTBNDRPG and PGM keyword)
When we go thru the EDIT MESSAGE FUNCTIONS on the message from the 2E Model, there is no way to put the extra spaces and when we try to modify the 2nd level text directly from the WRKMSGF command, the extra space does not translate to the source-generator.
CA 2E 8.x
Spaces between CRTBNDRPG and PGM are not allowed in scenarios where we want to add object specific compiler overrides.
Even a single space between them would lead to problems similar to what was mentioned, when trying to add object specific compile overrides. This is because, when we take option “O” to add compile overrides on the EDIT FUNCTION DETAILS screen, there is logic which builds out the entire *CRTBNDRPG command (from *MESSAGES file) along with any earlier defined compile overrides for that specific object and tries to prompt the complete CRTBNDRPG command. If we include spaces between CRTBNDRPG and PGM on the *Messages file, then this prompt functionality will break, leading to the error which was reported. There have been no changes carried out to this area since 1992, so it is in fact very stable code.
Also, the CA 2E documentation states the following:
RPGIV Generator Notes
The RPGIV ILE generator lets you create ILE programs and modules from generated RPGIV source. However, for version 7.0 of CA 2E, note the following details and limitations:
In the 3rd point above, It only talks about changing existing parameters/adding new parameters. It does not talk about changing the format of the message itself, which is what is being attempted.
If there are any concerns or questions regarding this topic, please do not hesitate to contact Broadcom Support.