Re: Service entry point SEP and 7.1

Jim, this is how I end up doing debugging on our 7.1 system, except for
those jobs that run too quickly.


Thanks, Matt

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Lowary, Jim
Sent: Thursday, November 03, 2011 9:50 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Service entry point SEP and 7.1

I don't have 7.1 but you might try seeing if you can manually start a
service job (STRSRVJOB ) to that other job and then do a Start Debug
(STRDBG ) just to see if it gives you any error messages that might give
you some clues (of course using the same user profiles).

Just a thought!

-- Jim

-----Original Message-----
message: 1
date: Wed, 2 Nov 2011 11:52:32 -0600
from: "Tyler, Matt" <matt.tyler@xxxxxxxxxxxxxx>
subject: [WDSCI-L] Service entry point SEP and 7.1

Has anyone run into problems getting SEPs to activate on their 7.1
systems?

The debug server is started and the SEP sets up just fine but whenever I
run any program I set a SEP for the debug view (almost) never activates.
I say almost because I cannot be 100% certain it has not in the past,
it's just not doing it now.

SEPs activate when connected to our 5.4 system in the same RDP 8.0.3
workspace function normally.

The connection properties between my RDP connections for the 5.4 and 7.1
systems are pretty close, the initial command program is different.

My user profile is close except for the special class being *SECOFR on
5.4 and *PGMR on 7.1.

Thanks, Matt

------------------------------