Session/Profile Parameter to avoid NAT0935 and NAT0936 ?

, ,
1

Hello all!

Somebody told me today, that Natural has a session/profile parameter for checking parameters of subprograms at compile time - to avoid NAT0935 and NAT0936 at runtime.

I read the documentation and didn’t find a hint. Is there such a parameter? I’ve never head about it. I think NAT0935 and NAT0936 are pure runtime errors.

Does anybody know something about that parameter?

Thanks!

Matthias

2

Take a look at the PCHECK parameter.

3

You live and learn… :slight_smile:

Thanks for the prompt reply.

4

Sorry again, but I can’t find out how to change this option…

The documentation talks about two things:

  1. The parameter module. But in NATPARM I got some compiler options like SM, DBSHORT etc. - but no PCHECK.
  2. The compilations options screen (called in natural via COMPOPT). There’s also no PCHECK-Option.

I’m using NAT 6.1.1.21 @ WinXP

Any ideas?

5

I’m using 6.3, where PCHECK is available in the configuration utility (NATPARMS) and in the compiler options (COMPOPT).

6

Even if I export the NATPARM as “NATPARM.LST” …

[COMPOPT]
 
DBSHORT = ON
ENDIAN = DEFAULT
GFID = ON
THSEP = OFF
PSIGNF = OFF
[COMPOPT-END]

BTW: It’s the same on our Nat 6.1.1.22 on Solaris.

Strange…

7

OK, maybe natparm exports the non-defaults only…

Here’s a list of my compiler options on NAT 6.1.1 @ WinXP:

CO
DBSHORT
DSLM
DU
FS
KC
SM
SYMGEN
SYNERR
THSEP
TQ
PSIGNF
ENDIAN
GFID
XREF

… but in the documentation, I can find more options like KCHECK, PCHECK, etc…

8

Today I got some time to install the community-Version of Natural (6.3.2) at my home PC (Win 2K). Here I found a PCHECK-Parameter.

If I stow a program with wrong parameters, I get a NAT0648 now.

But I don’t get this error if I change the Subprogram’s parameter - here I would still get a NAT0935 or NAT0936 at runtime.