You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
if you need to monitor started tasks on a bigger sysplex it is currently hard to tell on which system in the sysplex the STC is running. Have a look at the screen shot below
The STC AMICTL is running on 12 Members of the sysplex. If i need to have a closer look on one of them running on a certain LPAR, i have a hard time to find it. When you add the exec-data=Y flag to the z/OSM REST API request you will get among other useful data the field exec-member back. This will contain the name of the Plexmember (smfid) Take the contens of this field and add it to the jobs view for example like so:
JOBNAME(JOBID) - MEMBERNAME - STATUS
AMICTL(STC11223) - SYSX - ACTIVE
Thanks in advance
The text was updated successfully, but these errors were encountered:
Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.
@awharn yes you are right, but this is IMHO not even a deal at all ... it is no problem to check the z/os version! On big plexes displaying the smfid is a must!
Hi,
if you need to monitor started tasks on a bigger sysplex it is currently hard to tell on which system in the sysplex the STC is running. Have a look at the screen shot below
The STC AMICTL is running on 12 Members of the sysplex. If i need to have a closer look on one of them running on a certain LPAR, i have a hard time to find it. When you add the exec-data=Y flag to the z/OSM REST API request you will get among other useful data the field exec-member back. This will contain the name of the Plexmember (smfid) Take the contens of this field and add it to the jobs view for example like so:
JOBNAME(JOBID) - MEMBERNAME - STATUS
AMICTL(STC11223) - SYSX - ACTIVE
Thanks in advance
The text was updated successfully, but these errors were encountered: