Setting up an iASP on a customer system. When we look at the
QZDASOINIT job before there is any connection (it's still in PSRW,) we
see that it does NOT have the iASP designated. (Viewed in DSPJOB,
option 2, way at the bottom.)
Once a user has connected to the job (and the current user changes)
the disk pool is there. This is good, but we don't know why.
The only program that has yet run in the QZDASOINIT job is an RPGLE
stored procedure that ONLY sets up the library list with ADDLIBLE
commands. That program hasn't been compiled since 2007 and has no
knowledge of the iASP.
We suspected it was the Job Description of the user connecting to the
job so we tested that but that doesn't do it. A user with the iASP in
their JOBD who simply connects to iNAV thus causing ODBC activity does
NOT show the iASP in the QZDASOINIT job.
What is the magic that causes the iASP to be added to the QZDASOINIT
job? It's NOT SETASPGRP as that command is not being run in this job.
This is behaving as desired but we need to understand why!
This mailing list archive is Copyright 1997-2019 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