Seems that the APF-authorized load module also has to live in a linklisted
library (we don't use //STEPLIB in the logon proc).
Thanks again for all the attempts to help.
-jc-
--
For IBM-MAIN subscribe / signoff / archive acc
Got a frustrating puzzle here: An ISV product with an ISPF interface was
installed into libraries shared between two LPARs on different physical
CPUs
(both G5 machines). One LPAR was at z/OS 1.4, the other at z/OS 1.5. The
product installed and functioned correctly on both LPARs.
Now the (f
Oops, a premature send
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Mark Zelden
>
> On Wed, 7 Sep 2005 15:23:46 -0500, Chase, John
>
>
> >Can anybody suggest any ideas how to decipher what it can't find,
> >before I go thru the installation again?
>
> Yo
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Mark Zelden
>
> On Wed, 7 Sep 2005 15:23:46 -0500, Chase, John
>
>
> >Can anybody suggest any ideas how to decipher what it can't find,
> >before I go thru the installation again?
>
> You might want to start with
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Ed Finnell
>
> >>
> How do the ISV libraries get allocated? LOGON PROC, ISVALLOC
> CLIST, REXX Exec.
LOGON proc.
> Have those customizations been moved forward to the new LPAR?
Yes.
> Was there any security work
In a message dated 9/7/2005 4:00:21 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
Can anybody suggest any ideas how to decipher what it can't find, before I
go thru the installation again?
>>
How do the ISV libraries get allocated? LOGON PROC, ISVALLOC
CLIST, REXX Exec. Have those
On Wed, 7 Sep 2005 15:23:46 -0500, Chase, John <[EMAIL PROTECTED]> wrote:
>Can anybody suggest any ideas how to decipher what it can't find, before I
>go thru the installation again?
>
You might want to start with ISPF dialog function trace (opt. 7.7).
Mark
--
Mark Zelden
Sr. Software and Syste
Hi, All,
Got a frustrating puzzle here: An ISV product with an ISPF interface was
installed into libraries shared between two LPARs on different physical CPUs
(both G5 machines). One LPAR was at z/OS 1.4, the other at z/OS 1.5. The
product installed and functioned correctly on both LPARs.
Now
8 matches
Mail list logo