MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2012

RE: QUSLSPL API



fixed

My apologies.

APIError contains 272 for bytes available.

If it wasn't set correctly I wouldn't see messages CPF335D and CPF335E being returned by the api.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Crispin
Sent: Thursday, October 11, 2012 10:53 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: QUSLSPL API

Responded to this earlier but it hasn't come through.

You have defined APIError incorrectly, as far as I can see. It is blanks.
This means that BytesProvided is a huge number, and I think the API is blanking out all the parameters after APIError.

Define APIError like QUSEC and correctly initialize the Bytes Provided. This should fix the issue...

Crispin.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Thursday, October 11, 2012 1:30 PM
To: Midrange Systems Technical Discussion
Subject: RE: QUSLSPL API

Yes. If I drop the parameters after the API error data structure it works.

I just can't seem to get it to work when parameters 8 through 16 are included.

I know I'm missing something but I can't see it. This is why I asked if anyone had a matrix of the parms they would share.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gqcy
Sent: Thursday, October 11, 2012 10:24 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: QUSLSPL API

I use this api, but don't know much more than to ask this question.
you are creating the user space first? (QUSCRTUS)




On 10/11/2012 12:18 PM, Monnier, Gary wrote:
Nothing but 272 for bytes available. That is what is so frustrating.
No
messages in the job log either.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, October 11, 2012 10:16 AM
To: Midrange Systems Technical Discussion
Subject: RE: QUSLSPL API

What's in APIError?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Monnier, Gary"<Gary.Monnier@xxxxxxxxx>
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>,
Date: 10/11/2012 12:53 PM
Subject: RE: QUSLSPL API
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Thanks Gary.

I'm using format SPLF0300 and all the parameters so I can filter by
qualified job name and date/time range.

Using the following results in no entries being placed in the user space.

D lstSplF PR ExtPgm('QSYS/QUSLSPL')
D qualspacename 20A
D lfformat 8A
D lfusername 10A
D qualoutqname 20A
D lfformtype 10A
D lfuserspecdta 10A
D APIError 272A
D qualjobname 26A
D keyarray 10I 0 dim(1)
D nbrfldsrtn 10I 0
D ASPnumber 10I 0
D jobsysname 8A
D splfstartdate 7A
D splfstarttime 6A
D splfenddate 7A
D splfendtime 6A

Where

qualspacename = 'SPLFILES QTEMP ';
lfformat = 'SPLF0300';
lfusername = '*CURRENT';
qualoutqname = '*ALL';
lfformtype = = '*ALL';
lfuserspecdta = '*ALL';
qualjobname = *Blanks;
keyarray(1) = 0;
nbrfldsrtn = 0;
ASPnumber = -1;
jobsysname = '*ALL';
splfstartdate = '*FIRST';
splfstarttime = *Blanks;
splfenddate = '*LAST';
splfendtime = *Blanks;

Running

callP(E) lstSplF(qualspacename:lfformat :lfusername :
qualoutaname :lfformtype :lfuserspecdta:
APIError :qualjobname :keyarray :
Nbrfldsrtn :ASPnumber :jobsysname :
splfstartdate:splfstarttime:splfenddate :
splfendtime);

Results in no entries being written to the user space. No API error
is returned and there is no other error I can find.

Change splfstartdate to *ALL and splfenddate to *Blanks and the same
result occurs. Nothing is selected.

Blank out the dates and CPF335E is returned.

Blank out the job system name and CPF335D is returned.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Thursday, October 11, 2012 5:27 AM
To: Midrange Systems Technical Discussion
Subject: RE: QUSLSPL API

Maybe these links will help:

http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?info/apis/
QUSLSPL.htm


http://www.itjungle.com/fhg/fhg080305-story01.html

http://archive.midrange.com/rpg400-l/200306/msg00548.html

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx<
mailto:midrange-l-bounces@xxxxxxxxxxxx> [
mailto:midrange-l-bounces@xxxxxxxxxxxx]<mailto:[
mailto:midrange-l-bounces@xxxxxxxxxxxx]> On Behalf Of Monnier, Gary
Sent: Wednesday, October 10, 2012 5:18 PM
To: midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>
Subject: QUSLSPL API

All,

Does anyone have a matrix of the possible parameter combinations that
can be used with the QUSLSPL API? It seems every combination I try
results in no selections or a returned message ID.

Thanks,

Gary

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



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



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

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

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






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact