I think I understand better the IWP concept: Typically customers who have
isolated Websphere workload in a dedicated LPAR to control SW cost have
right now the possiblity to move this workload in a current LPAR (so
reducing the number of LPARs). That allows to not have to increase the
billed
You can use the _BPX_JOBNAME variable in a STDENV DDNAME for the FTPD proc.
for example if you are setting _BPX_JOBNAME=FTPDA then all client will be
named (forked) FTPDAn.
I hope this helps
Regards,
Jacky Hofbauer
zCost Management
www.zcostmanagement.com
I have all litterature on Al Shercow WebSte online then you can have a look
at http://www.zcostmanagement.com/media/skilldoc.html
so you have some tool but these tools will be just able to finalize your
cost control project.
There are risks and costs to a program of
.
A next step could be to control WLC by using SoftCapping, Group Capcity
Limit feature or our offer with AutoSoftCapping: a zCost Management product.
Jacky Hofbauer - zCost Management - voice: +33240854810 - web:
www.zcostmanagement.com - i...@zcostmanagement.com
There are risks and costs
Timothy, thanks for this update.
I don't understand how WLC increases for z/OS and IMS by one MSU and not for
CICS. Maybe, you consider CICS is running on one other Lpar which an equal
z/OS consumption?
To resume, I think new OOCoD records for z10 are very attractive because
you can fix your
OOCod two way (without the daily bill for HW: one amount/day/CP; less than
the full online CP):
1: IPLA: consider you VUs (Value Unit) with our IBM administrative account
manager; no more affect within your pre-negociation
2: MLC: sure the added capacity could affect your WLC bill (one peak on
.
Jacky Hofbauer
zCost Management
There are risks and costs to a program of action, but they are far less
than the long-range risks and costs of comfortable inaction.
John F. Kennedy
--
For IBM-MAIN subscribe / signoff / archive
Look ISFPRMxx member in your parmlib, your TSOAUTH RACF class access match
with your define group in ISFPRMxx
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message:
your SDSF server start with ISFPRMxx parmlib parameter.
Extract of this one, you have RACF access for TSOAUTH class and resources
JCL,OPER ACCT then, you receive this authoriezd functions
LOG,I,O,H,DA,DEST,PREF, ABEND,ACTION,INPUT,)
/***/
Shane
I think really that the Group capcaity Limit is the very good technical
tool but WLM make a basic MSU repartition to optimize resource sharing only
inside a group: in this fact, I think that it there not a relevant approach
to control the vWLC cost.
GCL gives a dynamic MSU management
Group Capacity Limit is a technical enhancements for z9 to falicitating
management.
and not a cost control enhancement.
It works inside a group and so it works overall for the CPC that if all the
lpar are in same and single group.
I think that it is not satisfactory but it is better than the
11 matches
Mail list logo
