Re: QWVRCSTK api returns value of N in Information-status field

I wonder if I should report this as a bug to IBM?

"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote in message
news:<mailman.1460.1232462474.21608.rpg400-l@xxxxxxxxxxxx>...
Thanks Carsten. unfortunately, I'm already using the value of 2. See
below:
D JobIDInfoDS DS
D JobName 10 Inz('*')
D JobUser 10 Inz( *Blank )
D JobNbr 6 Inz( *Blank )
D 16 Inz( *Blank )
D 2 Inz( *AllX'00' )
D 10I 0 Inz( 2 )
D 8 Inz( *AllX'00' )

D JobIDFmt S 8 Inz( 'JIDF0100' )

"Flensburg, Carsten" <Flensburg@xxxxxxxxxx> wrote in message
news:<mailman.1401.1232436686.21608.rpg400-l@xxxxxxxxxxxx>...
Hello Lim,

There's an option on the QWVRCSTK API job identification parameter
format JIDF0100 to specify that the stack information should be
retrieved for the initial thread of the identified job. If you haven't
already done so, you could try and set the Thread indicator in the
JIDF0100 job identification format to a value of 2, and see how that
turns out?

Best regards,
Carsten Flensburg

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai
Sent: 19. januar 2009 23:27
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: QWVRCSTK api returns value of N in Information-status field

Yikes!!! Not working. I changed my code to replace the QWVRCSTK api
with combination call to QMHSNDPM and QMHRCVPM api and getting the
CPF2479 (Call stack entry not found) error. I then tried changing the
CREATE FUNCTION to include NOT FENCED and still getting the same error.
Now, tell me why some people keep thinking that SQL is more superior
than RPG now :)?

Any suggest to get around this problem.

This communication is intended only for use by the addressee. It may
contain confidential or privileged information. If you receive this
communication unintentionally, please inform us immediately and delete
this e-mail and any attachments. Warning: Although we have taken
reasonable precautions to ensure no viruses are present in this email,
we cannot accept responsibility for any loss or damage arising from the
use of this email or attachments.
----------
----------