I'm curious to know what exact command you were running to test. Let me
explain why I am asking...
After every downtime we used to run the following four steps on every lpar
to verify that everything was still working.
Every since the downtime (we have extensive documentation) of 12/2016 we
stopped using Step Two (VFYSRVCFG). The reason being is that we
discovered that you could run a successful SNDSRVRQS *TEST, run VFYSRVCFG,
and SNDSRVRQS *TEST would no longer work. Turns out VFYSRVCFG was
corrupting stuff. I was pretty much instructed to stop using that
command. I cannot find the PMR number related to this.
Deleting and rebuilding the service configuration was the recommendation.
Software requirements have changed for service configuration after 7.1 to
include additional requirements.
These requirements, how to delete and rebuild service configurations, and
much more are available at
http://www-01.ibm.com/support/docview.wss?uid=nas8N1010756
Reading further is optional...
Downtime service verification steps:
Step one:
GO SERVICE
1. Change Service Agent attributes
Make sure that Enable is set to *YES. If already *YES, then F12 back to
Electronic Service Agent menu. If not, change it to *YES and enter
through the defaults.
Did you have to change it to *YES? ____________
10. Work with jobs
You should have at least the following 5 jobs:
Job User Type -----Status----- Function
QS9HDWMON QSRVAGT BATCH ACTIVE PGM-QS9HDWMON
QS9PALMON QSRVAGT BATCH ACTIVE PGM-QS9PALMON
QS9PRBMON QSRVAGT BATCH ACTIVE PGM-QS9PRBMON
QS9PRBSND QSRVAGT BATCH ACTIVE PGM-QS9PRBSND
QS9SFWMON QSRVAGT BATCH ACTIVE PGM-QS9SFWMON
If not, take “8. End jobs” to ensure that all are down. Then “9. Start
jobs”. When complete then another “10. Work with jobs”.
Step two: (Do not do anymore!)
VFYSRVCFG SERVICE(*ECS)
When complete page down through the messages at the bottom. Hopefully you
have:
Verify processing completed successfully.
If not, take a note here.
A few times lately I’ve had this run for over 5 minutes. If so, start
another session and telnet here or something. Find the original job you
were running this from. WRKUSRJOB QSECOFR *ACTIVE is one good technique.
Check the joblog. If you are seeing a lot of bad pointer messages then
Sys-Req out of the first job, sign off, and sign back on to start a new
job and try it again.
Step three:
SNDSRVRQS ACTION(*TEST)
If it works Rob “may” get a call from IBM to his extension. His extension
also rings on one phone in the Kendallville computer room. Sometimes the
local CE just emails Rob.
On 2016-09-14 Rob Berendt had an issue with GDI with SNDSRVRQS and
SNDPTFORD. He followed the steps in Corrective Action SYS16000013. If
you get an error, and upon further examination of the joblog you notice
“Point-to-point profile QVPN01IBM1 in use.” then it would behoove you to
peruse that corrective action.
Write down time _____________
Step four:
DSPPTF
Write down what you have for “Release of base option” _____________
If you wrote down V7R3M0 then
SNDPTFORD PTFID((SF98730))
Otherwise
SNDPTFORD PTFID((SF98720))
Enter defaults on first screen, 1=Send now on second screen.
WRKPRB
Top one should have a description of ‘Preventive service planning
information request‘
5=Display details
F9=Display PTFs
PTF ID Requested PTF Save File
SF987#0 Yes No
8=Display cover letter
and it should have a somewhat recent date in "the information in this
document was last updated : ".
Rob Berendt
midrange.com
