I did it several times recently.
Short answer: go for it.

Long answer:
1. LPAR name change can be related to your software contract, especially for NALC, etc. Solution: inform your IBM rep and ask them for contract appendix. It should be money-neutral (no new fees). 2. SMFID - a change will affect you SCRT report. However it is perfectly legal to have different SMFID on every day. In the past I used several SMFID per month on some LPARs. It wasn't a game, but real need - we were running short-living clones and different SMF ID allowed us to have unique value (no longer required) and some useful convention.
3. SYSNAME can be changed with no impact on the above.

However prepare for that. You should add new system name to your DFSMS definition *before* the change. Actually you may add more names than you really need. Also take care about system symbols. If you have SYS1.&SYSNAME..WHATEVER in any JCL then you should do something with that. It is less likely you use SMFID as a variable, but you should check it also. HealthChecker - the HZSPDATA dataset should be cleaned. Simply delete it and recreate as describe in the manual. Quick & dirty: allocate empty dataset, edit it with ISPF and issue SAVE on empty dataset. ;-)

BTW: it is also good moment to check and change other identifiers like JES node name, MAS member name, etc.


HTH

--
Radoslaw Skorupka
Lodz, Poland



W dniu 14.02.2023 o 17:18, Pommier, Rex pisze:
Hi,

I've been following the thread on LPARNAME, SYSNAME and SMFID with interest, 
namely because of a naming issue at my site that has been a minor irritation 
for me for years.  We run a small shop, 2 production LPARs not in a sysplex.  
One of the LPARs is set up as SYSNAME=SMFID=ZOS1.  Unfortunately the other LPAR 
has SYSNAME=ZOS1 but the SMFID=ZOS2.  What kind of headaches will I encounter 
if I change the SYSNAME on LPAR 2 to ZOS2?  I was told we will have issues with 
SMS and potentially SCRT?

TIA

Rex

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to