First, thanks for everyone giving ideas to solve the problem but now
every SEP I set is activating.
Looking over the SEP entries I have setup right now, all I can say is
that I made a mistake that I did not notice before. I did was remove
all SEPs and add new ones. Nothing special done to system
configuration, no IPLs; I have not even restarted my workspace.
Xuan, It seemed that no matter what SEP I setup it was not activating,
except for the CGI program I mentioned earlier. As I mention above I am
now thinking it was me that configured the SEP wrong in some fashion.
Sorry for wasting time on this one.
Thanks, Matt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Xuan Chen
Sent: Thursday, November 03, 2011 11:43 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
Matt,
Could you please explain your SEP situation in more details?
That is the scenario I deducted from your note:
************************************************************************
*****
You use your profile to logon to RSE (for example, I use MATT to refer
to
your user id). You set a SEP on a program which will be invoked by CGI.
You did not change the user id of the SEP to QTMHHTP1 (this is the user
id
used to run the CGI program). When you launch your application, your
SEP
is not hit.
************************************************************************
*********
Is this the scenario described correct? If not, please let me know.
If you want to use SEP to debug a program invoked by CGI, you probably
need
to do one of the following (Assuming CGI program is running under user
profile QTMHHTP1):
1.
Connect to RSE using user id QTMHHTP1. Set SEP on the program you want
to
debug. Run CGI. SEP should be hit.
2.
Connect to RSE using your user id MATT.
Set SEP on the program you want to debug.
Go to Service Entry Point view, right click on this SEP and choose
Modify.
In the dialog, change the user id to QTMHHTP1 (user profile MATT should
have *USE authority on user profile QTMHHTP1).
Run CGI. SEP should be hit.
Thanks,
Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
"Tyler, Matt"
<matt.tyler@winco
foods.com>
To
Sent by: "Rational Developer for IBM i /
wdsci-l-bounces@m Websphere Development Studio
Client
idrange.com for System i & iSeries"
<wdsci-l@xxxxxxxxxxxx>
cc
11/03/2011 12:16
PM
Subject
Re: [WDSCI-L] Service entry point
SEP and 7.1
Please respond to
Rational
Developer for IBM
i / Websphere
Development
Studio Client
for System i &
iSeries
<wdsci-l@midrange
.com>
Xuan,
I have attempted to activate a SEP using _my profile_
and
QSYSOPR with no luck. I am able to use QTMHHTP1 to debug CGI pgms.
Thanks, Matt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Xuan Chen
Sent: Thursday, November 03, 2011 9:18 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,
When setting/running SEP, there are two user profiles involved. First,
the
setter's user profile, and this is the user profile you used for RSE
connection. For runner's user profile, by default, it is set to the
same
as the setter's profile, but you can change it in Service Entry Point
view.
I don't think you need *SERVICE authority to set/run SEP. I remembered
there used to be a problem if your setter and runner are of different
user
profiles, and you need *SERVICE authority, but this problem should be
fixed
long time ago.
Please make sure the user id you used to run the application (where SEP
will be hit) is the same as the user profile you used to logon to RSE
(then
to set SEP). Please let me know if they are the same, but you still
have
problem.
Thanks,
Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
"Tyler, Matt"
<matt.tyler@winco
foods.com>
To
Sent by: "Rational Developer for IBM i /
wdsci-l-bounces@m Websphere Development Studio
Client
idrange.com for System i &
iSeries"
<wdsci-l@xxxxxxxxxxxx>
cc
11/03/2011 10:22
AM
Subject
Re: [WDSCI-L] Service entry point
SEP and 7.1
Please respond to
Rational
Developer for IBM
i / Websphere
Development
Studio Client
for System i &
iSeries
<wdsci-l@midrange
.com>
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.
--
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.
--
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.
--
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.
midrange.com
