Unsolved
This post is more than 5 years old
5 Posts
0
436
Updating cpu product codes
All the products seem to expire today so I contacted EMC and got new product codes.
CSL 9.0 seems fine.
For PSP 3.1.0, after assembling the new product code, the manual says I need to recycle PSP (SWSCTL21) after issuing a F LLA,REFRESH. If I do this will it affect anything in VCP or Terasam which are running.
Since VCP is started with the product code in the jcl, how do I update the prod-code while VCP is still running ?? I don't see any explanation in the manuals.
Terasam 3.2.3 seems to be OK after reassembling TS$CPUTB, then F lla,refresh, then I reran the Ts$init with the requeue=table and it didn't issue the expiration message so I have to assume this new one has taken affect.
Questions seem to be on PSP 3.1 and VCP 1.4.1 only.
thanks,
John c
CSL 9.0 seems fine.
For PSP 3.1.0, after assembling the new product code, the manual says I need to recycle PSP (SWSCTL21) after issuing a F LLA,REFRESH. If I do this will it affect anything in VCP or Terasam which are running.
Since VCP is started with the product code in the jcl, how do I update the prod-code while VCP is still running ?? I don't see any explanation in the manuals.
Terasam 3.2.3 seems to be OK after reassembling TS$CPUTB, then F lla,refresh, then I reran the Ts$init with the requeue=table and it didn't issue the expiration message so I have to assume this new one has taken affect.
Questions seem to be on PSP 3.1 and VCP 1.4.1 only.
thanks,
John c
Davidy8s
154 Posts
0
September 30th, 2009 09:00
TeraSAM & VCP both use JCL to update the CPU code. So for VCP, you can either overlay the cpu code in the JCL, or, add another cpu code. You can enable VCP without disabling.
For PSP, you will need to update the cpu code (assemble), REFRESH LLA, stop the subsystem, then start the subsystem.
For all the router products, the cpu code (license) is checked at the time of enable, it's just that PSP uses a subsystem running as a started task, so that adds a layer of complexity...
Let me knof if you have further questions...
Best regards,
Dave Yates
EMC TSE3
Benevolent Host S/W & Mainframe Forum Moderator
"Il Moderatore Benevolo"
Mrloser
5 Posts
0
September 30th, 2009 09:00
I now understand that I must recycle SWSCTL21 for PSP to obtain new cpu code but we run VCP as a proc (started task):
//VCP PROC
//*
//VCP141 EXEC PGM=VCPINIT,
// PARM=('ENABLE,PROD14,NOSTATS,NORLSE,NOESDS',
// '548750446256') 2096-Q04 EXP 09/30/2009
//*
//SOFTLIB DD DISP=SHR,DSN=PSI.VCP.LINKLIB
//CONREP DD DISP=SHR,DSN=PSISP.VCP.REL141.CTLREP.PSI1
//SYSPRINT DD SYSOUT=*
//CCTLIB1 DD DUMMY
//CCTLIB2 DD DUMMY
=====================================================
If I just start it again with the newer prod-code will it work correctly ??
John
Davidy8s
154 Posts
0
September 30th, 2009 09:00
I now understand that I must recycle SWSCTL21 for
PSP to obtain new cpu code but we run VCP as a proc
(started task):
/VCP PROC
...
If I just start it again with the newer prod-code
will it work correctly ??
John
Yes, that's correct. Basically a "zero down time", re-enabling of VCP.
Dave Yates
EMC TSE3
Benevolent Host S/W & Mainframe Forum Moderator
"Il Moderatore Benevolo"
Mrloser
5 Posts
0
September 30th, 2009 11:00
That seemed to work fine. I was just a little leery about any update to VCP on the fly.
Thanks for your help,
John C