Hello Lawrence,
It is true that today the SMSROUTE value length is of 4 characters and so you have troubles to use symbols.
However, even if it is not nice, you can get it working.
I tested today with the symbol defined as follow:
SYSDEF SYMDEF(&L_.='ABCD')
The result after refresh is good:
SMSROUTE | &L_. | ABCD
So that means that you will have to have a unique character to differentiate the Lpars from each others. I think that you can use it like that for now.
On another hand, we should review the possibility to increase the SMSROUTE length size when the first character is an ampersand(&) as we will have a symbolic substitution.
This is a very good idea, thank you.
I will let our Vantage team to provide an update on this request.
Have a try with my solution and let me know.
Pierre Montel
------------------------------
Pierre Montel
Principal Support Engineer
Broadcom
CA Deutschland GmbH | Marienburgstraße 35 | 64297 Darmstadt
office:+49 (941) 29784186
pierre.montel@broadcom.com | broadcom.com
HRB Darmstadt 1706 | Geschäftsführer: Holger Stickl, Deborah Streeter
------------------------------
Original Message:
Sent: 09-09-2020 04:35 AM
From: Lawrence Bulley
Subject: CA-Vantage SMSROUTE in a GDPS environment
We run a GDPS environment and we want to use ADDOVRP to automatically add volumes into storage groups. Our system programmers do not want to use System Group Names and prefer that we use a system symbolic.
Is it possible for an enhancement for SMSROUTE in VKGPARMS to use a system symbolic?
For instance, in IEASYM00 code SYMDEF(&NK_.=LPR1,LPR2,LPR3,LPR4), and in VKGPARMS code SMSROUTE (&NK_.)?
We cannot use SMSROUTE (*ALL), as the disks must not be varied online to our GDPS K-Lpars.
------------------------------
Lawrence Bulley
------------------------------