Comments on: H Spec

By: tomliotta

tomliotta — Tue, 23 Nov 2010 02:56:24 +0000

You can add a default H spec with various options…

True. Unfortunately none of the options will set the compiler DBGVIEW() parameter. And I haven’t quite come up with a good reason for having it done. It doesn’t seem to me to be useful for individual programs when the command can be used as needed.

Tom

By: graybeard52

graybeard52 — Tue, 23 Nov 2010 00:46:17 +0000

You can add a default H spec with various options, depending what you need. For example if you put

Option(*SRCSTMT:*NODEBUGIO:*XREF)

in the data area QRPGLE/DFTLEHSPEC this H-spec will get included in every RPGLE compile, unless the H-spec is specfically included.

By: tomliotta

tomliotta — Sun, 21 Nov 2010 11:10:25 +0000

why not just do as WaltZ400 said and just change the command default…

Because an H-spec affects a specific program permanently (until the H-spec is changed). Changing a command default affects every program compiled from then on, and upgrades or PTFs can remove the changed default. When you want a specific program to have options, it doesn’t make much sense to set every other program the same way.

Tom

By: teandy

teandy — Mon, 07 Dec 2009 21:32:24 +0000

My question would be, why not just do as WaltZ400 said and just change the command default to something like this?


CHGCMDDFT  CMD(CRTBNDRPG) NEWDFT('DBGVIEW(*ALL)

By: tomliotta

tomliotta — Mon, 07 Dec 2009 03:29:04 +0000

DBGVIEW() is an option for the system debugger, not a RPG option. DBGVIEW() isn’t specific to a given programming language.

Debug options in RPG source code are more directed to support supplied by the RPG compiler rather than by the system itself.

If the options were available in source code, how would you expect the command parameter to work? If the command parameter said *LIST and program source said *NONE, which would you expect to have precedence?

BTW, please don’t ask two unrelated questions in a single post. It makes it extremely difficult for others who come later to search for useful answers.

Tom

By: geneburns

geneburns — Fri, 19 May 2006 17:11:58 +0000

Q1. Can we define the compile option – debugging view (DBGVIEW) = *all in H spec ???

Would this be what your are looking for?
OPTION(*SRCSTMT)

If *SRCSTMT is specified, statement numbers for the listing are generated from the source ID and SEU sequence numbers as follows:

stmt_num = source_ID * 1000000 + source_SEU_sequence_number
For example, the main source member has a source ID of 0. If the first line in the source file has sequence number 000100, then the statement number for this specification would be 100. A line from a /COPY file member with source ID 27 and source sequence number 000100 would have statement number 27000100. *NOSRCSTMT indicates that line numbers are assigned sequentially.

By: edi4colorado

edi4colorado — Thu, 18 May 2006 09:18:45 +0000

No, you cannot code a control spec so that it compiles as debug *yes.

By: uppikal

uppikal — Thu, 18 May 2006 01:42:28 +0000

Thanks very much for the %DATE solution !!!

but what I ment by H-Spec is the control specification declaration spec in RPG. e.g.

… 1 …+… 2 …+… 3 …+… 4 …+… 5 …+…
HOPTION (*NODEBUGIO)

so, now while compiling the program we need not define *nodebugio. This declaration will take care off..
Similarly can we declare for dbgview ??

Thanks and regards,
Kalpesh