For QSYS objects, at version 7.1 and greater.
RTVOBJD OBJ(L/O) OBJTYPE(T) ASPDEV(ASP *ASP) ASP(ASP) LIBASP(LIBASP)
-Matt
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Monday, May 8, 2017 8:29 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: iASP causing commands to fail
In our team meeting this morning, the developer in charge of implementing our DR solution described a problem in testing the CPYTOSTMF command. When a library that is specified in the FROMMBR parameter is moved to an iASP, the command no longer works unless the existing FROMMBR parameter is prefaced with the name of the iASP. For example,
FROMMBR('/QSYS.LIB/ALIB.LIB/OUT.FILE/OUT.MBR')
must be changed to
FROMMBR('/MEDIASP/QSYS.LIB/ALIB.LIB/OUT.FILE/OUT.MBR')
Furthermore, he implied that there is no way to programmatically determine whether an object is in an iASP and/or the name of the iASP. Since I have no experience with iASPs, I can't vouch for the veracity of that, but it seems unlikely to me that IBM didn't give us a way to make that determination. From this implication, he believes that we won't be able to change the hundreds of our programs that use CPYTOSTMF until and immediately following moving the affected libraries to the iASP.
The help text is silent on this matter, other than sending me on a fishing
expedition: For more information on specifying path names, refer to "Object naming rules" in the CL topic collection ... <in Infocenter>", where I am led to the "Programming CL overview and concepts" manual and, specifically, the section labeled "Object naming rules". Nothing on iASPs.
Is there a simple way to determine whether an object is in an iASP and, if it is, the name that must be used in the FROMMBR parameter? Are there other commands that we will find this same issue?
- Dan
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
