When you define your CFRM policy using IXCMIAPU you can point to your newly
created CFRM CDS as Such:
DATA TYPE(CFRM) REPORT(YES)
DSN(Your newly created CFRM CDS name)
DEFINE POLICY NAME(policyname here) REPLACE(YES)
Etc..
That populates the newly cr
George,
If you follow this Link:
https://www-304.ibm.com/servers/resourcelink/lib03060.nsf/pages/lsprzOS11MIJuly2010?OpenDocument&pathID=
It will give you a table in which you will see PCI values and their MSU
equivalent for all Supported zSeries processors. At the top of the Web page
there is a
PCI - Processor Capacity Index - First calculated/Introduced with the z/OS V1R9
LSPR(Large Systems Performance Reference).
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of George Henke
> Sent: Friday, February 17, 2012 08:29 AM
> To:
Greetings Bill,
Have you looked at Licensing Connect:Direct by the number of connections rather
than where it runs. Not knowing your configuration I cannot know if this will
help or make it worse.
Regards,
Jihad K Kawkabani
-Original Message-
From: IBM Mainframe Discussion List [mailto:IB
Kerberos is not required, I have a similar Informational message but the client
works just fine. Here is the Kerberos informational message I get:
GFSC284I NETWORK FILE SYSTEM CLIENT COULD NOT GET GSS CREDENTIALS
FOR THE NFS CLIENT : GSS API krb5_get_in_tkt_with_keytab() FAILED
WITH GSS MAJOR STAT
Matt,
Can you share what is in your BPXPRMxx parmlib member for FILESYSTYPE
TYPE(NFS).
Also is "SYS1.NFSLIBE" in your LINKLIST and APF authorized?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Dazzo, Matt
Sent: Monday, August 01, 20
RSA key file permissions must be preserved to what they were when the key was
generated. Do not change the permissions of the RSA key file when copying to
another user's ssh directory
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Mark
7 matches
Mail list logo
