Re: SDM1002 on Service Agent connect via VPN -- MIDRANGE-L

Have you reported this to IBM?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Neil Palmer <NeilP@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/10/2004 07:14 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: SDM1002 on Service Agent connect via VPN






A follow up with a circumvention.  Looking at the unnecessary attempt to 
check the config status of line QESPPLIN I figured "why not create a dummy 

line description and call it QESPPLIN ?"

SO - here's the QSDPRBMON joblog after doing this to circumvent the bad 
IBM code in Service Director:

    118 - RTVCFGSTS CFGD(QESPPLIN) CFGTYPE(*LIN) STSCDE(&LINESTS) 
    166 - SNDSRVRQS ACTION(*PRBID) RMTCPNAME(*IBMSRV) RMTNETID(*NETATR) 
   PRBID('0404172371') 
 Sending service request 0404172371. 
 Service request processing complete. Contact your service provider. 
 Problem reporting complete. Service number is 57441. 
    184 - RTVCFGSTS CFGD(QESPPLIN) CFGTYPE(*LIN) STSCDE(&LINESTS) 
        - RETURN        /* RETURN due to end of CL program */ 


Just finding QESPPLIN satisfies the program and it carries on and 
(successfully) does the SNDSRVRQS command - which uses the VPN Internet 
connection and works fine !  :-)

...Neil





Neil Palmer <NeilP@xxxxxxxxxxx> 





To

cc

Subject
Re: SDM1002 on Service Agent connect via VPN






It appears the QSDPRBMON job is too stupid to even look for the Universal 
(VPN) Connection, and dies simply because there is no dial-up PPP line 
configured.  (I did have an SDLC QESLIN configured, it didn't like that 
and didn't like it when I deleted it either).

This is from the joblog of the QDSPRBMON job:

    118 - RTVCFGSTS CFGD(QESPPLIN) CFGTYPE(*LIN) STSCDE(&LINESTS) 
 Object QESPPLIN in library QSYS not found.      << CPF9801>> 
    155 - DLYJOB DLY(300) 

and this is logged to QSYSOPR msgq at same time:

Message ID . . . . . . :   SDM1002       Severity . . . . . . . :   80 
Message type . . . . . :   Information 
Date sent  . . . . . . :   02/10/04      Time sent  . . . . . . : 18:24:39 


 
 
Message . . . . :   Service Agent is not able to place a service call - 
action 
  required. 
Cause . . . . . :   Service Agent is trying to place a service call, but 
is 
  not able to place it. 
Recovery  . . . :   Check the ECS line description (QESLINE), modem, and 
 
  telephone line. Service Agent cannot place a service call if the ECS 
line 
  description, modem, or telephone line is being used by another job. If 
 
  possible, make the ECS line description, modem, and telephone line 
available 
  to allow Service Agent to place the call. If the ECS phone line, modem, 
and 
  line description are available, there may be a problem. Contact your 
local 
  IBM Service Representative. In the United States, call 1-800-IBMSERV. 
You 
  may also be able to make use of the Service Agent Line Monitoring 
function. 


It will not send the PREPARED problem, but if you run SNDSRVRQS *PREPARED 
(which is what documentation I've found on IBM's web site says is 
basically what Service Director/Agent is SUPPOSED to do) the problem is 
successfully reported via the VPN connection.


>From the Electronic Service Agent main menu (QSDMAIN) option 3 goes to 
the 
Inventory Collection menu.  If you try to run #5 from that menu, and take 
option 2 to change, you get this command:

                    CHANGE SERVICE CONFIGURATION (CHGSRVCFG) 
 Type choices, press Enter. 
 CONNECTION TYPE  . . . . . . . .                 *PTP, *VPN 

If you enter *VPN you get:

Message ID . . . . . . :   CPF9897       Severity . . . . . . . :   40 
Message type . . . . . :   Diagnostic 
Date sent  . . . . . . :   02/10/04      Time sent  . . . . . . : 17:27:0
Message . . . . :   VPN IS NOT CURRENTLY SUPPORTED BY THIS COMMAND. 
Cause . . . . . :   No additional online help information is available. 
>From program . . . . . . . . . :   QYSDWKSRV 
  From library . . . . . . . . :     QSYS 
  From module  . . . . . . . . :     QYSDWKSRV 
  From procedure . . . . . . . :     Send_error_message__FPc
  From statement . . . . . . . :     4444 

...Neil




Neil Palmer <NeilP@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
2004/02/10 03:23



To

cc

Subject
SDM1002 on Service Agent connect via VPN






I have several V5R2 systems with Service Agent (Service Director) 
configured, and the connection to IBM via external 7852 modems (SDLC 
dial).  Works fine - Service Director places Test calls, does the 
automatic PTF check weekly - no problems.

On a couple of systems I configured IBM Universal Connection (VPN over 
Internet).  SNDPTFORD and SNDSRVRQS *TEST work fine over the VPN 
connection.  Service Agent refuses to connect and issues SDM1002 messages 
(not able to place a service call).  I've been testing by creating a Test 
problem.  WRKPRB shows the test problem as OPEN, and within a minute 
changes to PREPARED - and QSYSOPR shows the SDM1002 error message.  I can 
run SNDSRVRQS *PREPARED and the PREPARED problem is SENT, but Service 
Director refuses to do this itself.  Any clues ?

...Neil




_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.