Qshell has command dataq , where option -w is for writing
see:
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_72/rzahz/rzahz.pdf

IMO usage is somethinng like this:

dataq -w /qsys.lib/MyLib.lib/MyDataQ.dtaq "data to write"

So in COBOL using declarations like this

01 QCMDEXC-ARGS.
05 CL-CMD PIC X(100).
05 PACK-VAL PIC 9(10)V9(5) COMP-3 VALUE 100.

you can store into a string CL-CMD the command like this:

QSHELL('dataq -w /qsys.lib/MyLib.lib/MyDataQ.dtaq "data to write" ')

with the command length PACK-VAL and call it:

CALL 'QCMDEXC' USING CL-CMD PACK-VAL
ON EXCEPTION
...
NOT ON EXCEPTION
...
END-CALL

Trapping CL/QSH-command errors should work here.

Maybe this approach should be simpler, than wrapping API call into a CL and call the CL form COBOL.


-----"COBOL400-L" <cobol400-l-bounces@xxxxxxxxxxxx> píše: -----
Komu: cobol400-l@xxxxxxxxxxxx
Od: Vinay Gavankar
Odoslal: "COBOL400-L"
Dátum: 03.06.2016 01:34
Predmet: [COBOL400-L] Trapping QSNDDTAQ errors in Cobol program


Hi,

I am an occasional Cobol user, and was wondering how I would go about
trapping an error returned by the QSNDDTAQ API called from a Cobol program.

We want to trap the condition when Data Queue is full (CPF950A) and go in a
DLYW before trying again.

I think calling a CL program from the Cobol to call the API, instead of
calling the API directly might work, but I have been told to check if it is
possible to do without adding a new CL program call.

I tried ON EXCEPTION clause, but that seems to trap only errors on the Call
command (program not found, parameter mismatch etc), so does not work in
this case.

Any suggestions, guidance will be greatly appreciated.

Vinay

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.