× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



No there's no policy at our company but your right, I probably should
just stick with doing my debugging on the development environment.
Thought I would test & debug against the good production data to save a
little time. :-) A while back, I think I had to install it on the Dev
side but didn't on Production because I was new to WDSC and didn't want
to take any chances.

Thanks for your help.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Vern Hamberg
Sent: Wednesday, May 06, 2009 9:32 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Command STRRSESVR in library *LIBL not found

Larenzo

I'm not sure - is there a policy at your company about developers
working in the production side? It really should be very restricted. The

product just might not be installed on the production side.

You might try the DSPSFWRSC command on both and compare

After that, you have to find out what was installed or not, and why.

Vern

Larenzo Alexander wrote:
Thanks, I did the WRKOBJ *ALL/STRRSESVR and it shows a STRRSESVR *CMD
object in QDEVTOOLS library in my Production Environment but when I do
a
WRKOBJ *ALL/STRRSESVR in my Development Environment it shows two
STRRSESVR objects, one in QDEVTOOLS library and one in QSYS library.
So
would I just need to copy the one in QDEVTOOLS to QSYS?

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Vern Hamberg
Sent: Tuesday, May 05, 2009 9:26 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Command STRRSESVR in library *LIBL not found

Do a WRKOBJ *ALL/STRRSESVR and see whether it exists on your system.

Larenzo Alexander wrote:

Can someone point me in the right direction of what I need to check

into

to determine the cause of this error message?



I'm using WDSC 6.0.1, I have debugged before on our development
environment but this is my first time trying to debug on the

Production

environment. When I try to enter the command STRRSESVR NAME('AS400XXX

-

Production') from the 5250 session, I get the message in subject.



Thanks in advance.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.