I do not have *SERVICE authority on our 5.4 system and I did not see anything in the memo to users about that, for 6.1 and 7.1.
Thanks, Matt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Austin, Mark
Sent: Thursday, November 03, 2011 2:35 AM
To: Rational Developer for IBM i / Websphere Development Studio Client forSystem i & iSeries
Subject: Re: [WDSCI-L] Service entry point SEP and 7.1
Hi Matt,
If I remember rightly, you need *SERVICE special authority to use SEPs.
Best regards, Mark
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Tyler, Matt
Sent: 02 November 2011 17:53
To: wdsci-l@xxxxxxxxxxxx
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
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
“**Confidentiality**
The information contained in this e-mail is confidential, may be privileged and is intended solely for the use of the named addressee. Access to this e-mail by any other person is not authorised. If you are not the intended recipient, you should not disclose, copy, distribute, take any action or rely on it and you should please notify the sender by reply. Any opinions expressed are not necessarily those of the company.
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you.
midrange.com
