RE: Retrieve System Time Information (QWCRTVTM) API - Error code parameter length -- MIDRANGE-L

IBM AJS actually has predefined parameters, however, you can only see them if viewing an AJS job in iNav, not in green screen.
AJS has a QTIME parameter.
Neither QWCRTVTM API nor custom CL program no longer needed.
A simple CHGDTAJS PARM(STRTIM) PARMDATA(&QTIME) in the beginning of the AJS job.

Also see this good link supplied by IBM support.
Table 1 shows all the predefined AJS parameters.

Passing Parameters in Scheduled Jobs
http://archive.ibmsystemsmag.com/ibmi/administrator/systemsmanagement/passing-parameters-in-scheduled-jobs/

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Charles Wilt
Sent: Friday, August 30, 2019 3:34 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Retrieve System Time Information (QWCRTVTM) API - Error code parameter length

you have to initialize the bytes provided...

Personally, I'd use 0 in this case, that would cause an exception to be thrown if an error occurs.

CALL PGM(QWCRTVTM) PARM(TIMERECV TIMERECVL TIMEFORNM TIMENUMF TIMEKEYF x'00000000' ).

Charles

On Fri, Aug 30, 2019 at 1:00 PM Steinmetz, Paul via MIDRANGE-L < midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>> wrote:

I'm call the API from AJS, Advanced Job Scheduler.
Error Code (TIMEERRCD) defined as 12.

CALL PGM(QWCRTVTM) PARM(TIMERECV TIMERECVL TIMEFORNM TIMENUMF TIMEKEYF
TIMEERRCD).

API is failing, error code not valid.

Message . . . . : Error code parameter not valid.

Cause . . . . . : The format of the error code parameter is not
correct.
Recovery . . . : Correct the error code parameter and try the
request
again. If you do not know the correct format for the error code
parameter,
see the APIs topic collection in the Programming category in the IBM
i

Information Center, http://www.ibm.com/systems/i/infocenter/.

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of
Charles Wilt
Sent: Friday, August 30, 2019 12:14 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
Subject: Re: Retrieve System Time Information (QWCRTVTM) API - Error
code parameter length

It's the standard API error structure...

https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/apiref/err
orcodeformat.htm

Has to have at least Bytes Provided, if set to 0 then the API will
throw an exception.

dcl-ds errorCode qualified inz;
bytesProvided int(10) inz(0);
end-ds;

12 bytes and you get the error message ID dcl-ds errorCode qualified inz;
bytesProvided int(10) inz(%size(errorCode));
bytesAvailable int(10);
errorId char(7);
end-ds;

more than 12, and you can get back the message description (don't
forget the reserved field at pos 13) dcl-ds errorCode qualified inz;
bytesProvided int(10) inz(%size(errorCode));
bytesAvailable int(10);
errorId char(7);
*n char(1);
errorText char(80);
end-ds;

Charles

On Fri, Aug 30, 2019 at 9:57 AM Steinmetz, Paul via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>> wrote:

For the Retrieve System Time Information (QWCRTVTM) API What is the
length for the Error code parameter?

https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/apis/qwc
rt
vtm.htm

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com