RE: CA API toolkit

[Buck Calabro/commsoft<mcalabro@xxxxxxxxxxxx>]

>First, MSVC v2.0 is quite a bit down level. 
>Version 6.0 is the current release.  I would recommend 
>you upgrade to that before going to far. 

We had to use *some* MS product because the sample
code comes with an MS-only compatible library.  One
of our PC folks had a copy of 2.0 and it did compile 
the code...

>As far as your problem, is the user that signed on 
>when starting the Client Access router (aka: the "common" 
>user ID) CMILLER? 

CMILLER was signed on and CMILLER was trying to view one 
of CMILLER's files, so security does not seem to be
an issue, AFAIK.

Looking back at the message:
1314: Unable to open file! "QPJOBLOG/461/QPRTJOB/019150/CMILLER/"

it appears as if the list API is not passing the DSPSPLF
API the system name.  The proper syntax for CWBVIEWR is
splfname/splfnbr/jobname/jobnumber/username/systemname

Not having done much Windows programming, I can't really
help our PC folks debug this (I am helping on the 400
side of things)  Basically, the list API creates a list
of spooled files (exactly like Ops Nav does) and when
one clicks on an individual entry, the list API calls
the display API, passing it a handle to the individual 
list entry (spooled file) that one clicked on.

For whatever reason, the display API doesn't seem to be
getting/finding the complete parameter, including the
system name.

I could not find any Redbooks online that address this.

Buck Calabro
CommSoft, Albany, NY
mailto:mcalabro@commsoft.net




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---