«
»

Service Agent on V5R4 or V5R3 with newer CUM

1. February, 2007

I’ve always hated the IBM service agent. But with V5R4, it has become usable. Not good, but working. I still think that IBM lacks quite a lot of documentation when it comes to setting up service agent for a first time. If you’re in this helpless situation as i was, here’s my short list on how to get it working.

  • Setup TCP/IP, you will need a default route, name servers, etc.pp. ping 'www.google.com' should work
  • Use WRKCNTINF to set contact information
  • Set the system value QRETSVRSEC to 1
  • Create a duplicate of QSECOFR and logon as that user – i usually call this one QESAADM
  • Logon as QESAADM
  • Type GO SERVICE, and answer the country questions
  • If you did everything correctly, you should be in the SERVICE menu
  • Go back, and use SNDSRVRQS *TEST to send a test request – the first one will take lots of time, and a java job named QESECARE will run for a few minutes
  • Use to job scheduler to submit the scheduled job QS9AUTOTST right now.
  • Have a look at the QSYSOPR MSGQ, and at the WRKPRB output to see if everything worked.

If you have some problem’s, they’re probably related to a missing crypto option (5722-AC3 on V5R3, V5R4 does not need one). Other causes can be connection problems like restrictive firewalls. See WRKTCPPTP – QLCLDIAL* for Dial Up connections, and QVPNIBM* for VPN connections. Especially the spool files of these job containing valuable debug information.

Category: IBM i, POWER  |  Comment (RSS)  |  Trackback

Leave a comment