Re: [sqr-users] Sporadic error (SQR 3301) Program stopped byuserrequest.

["Joe Johnson" <jej1216@hotmail.com>]

TP,

Thanks for clarifying - my original post was that I was getting the error 
and the only log entry I found was the warning - I wasn't sure if it was 
related but it was all of the log entries I could find that indicated 
anything being a problem.

The Process Scheduler config file was not changed at all between the time 
the SQR did not bring the "Program stopped by user request" error and when 
it did.  Also, I rebooted the Process Scheduler before I posted this issue 
just to cover that possibility.

In the SQR, I have no STOP code other than the included SQC's that I listed 
previously.

I have compared my #includes and my #Return-Status to a similar interface
program that does not present this issue,
and nothing seems amiss.

Initialization Procedure sets this: move 1 to #Return-Status
End-Process Procedure: let #return-status = 0

I set my beginning include to #include 'setenv.sqc'

My end includes are:

#include 'curdttim.sqc'
#include 'datetime.sqc'
#include 'number.sqc'
#include 'reset.sqc'
#include 'prcsdef.sqc'
#include 'prcsapi.sqc'
#include 'stdapi.sqc'
#include 'datemath.sqc'
#include 'rotname3.sqc'

Additionally, this SQR works flawlessly in our PRD environment and up until 
yesterday morning worked in our DEV/TST environment. Then, with no SQR code 
change, it started returning the error. An hour later, it stopped returning 
the error and has worked ever since. Another interface SQR with the exact 
same #return-status and #includes works without issue in both the PRD and 
the DEV/TST environments.

I can post the SQR code, but since it worked every time except for this one 
mystery hour, I am trying to focus on what changed since the SQR code did 
not and the Process Scheduler config file did not.  Other than looking for 
any log entry errors I can't come up with how else to troubleshoot this.  I 
use debug statements in the SQR for both program flow and for data display 
and that did not shed any light for me.

I'll pursue the Process Scheduler issue elsewhere but I need assistance in 
further trouble-shooting the SQR error.

Thanks,

jej1216


--------------------------------------------------
From: "T P" <bebabble@yahoo.com>
Sent: Wednesday, March 18, 2009 9:04 AM
To: "This list is for discussion about the SQR database reporting 
languagefrom Hyperion Solutions." <sqr-users@sqrug.org>
Subject: Re: [sqr-users] Sporadic error (SQR 3301) Program stopped by 
userrequest.

> The warning from the process scheduler log has nothing to do with your sqr 
> problem.  They are two separate issues entirely.  The warning is correct 
> and you just need to properly reconfigure your scheduler using the psadmin 
> utility for it to "pickup" any changes made to the config file as bouncing 
> it doesn't perform the reconfigure steps.  In the warning it is saying 
> your current configuration is ONLY booting 3 PSAESRV services (count them 
> in the os to verify the warning is correct) but 5 are needed to support 
> your server definition.
>
> The sqr error "Program stopped by user request" usually means some program 
> criteria has been met to exit the program instead of continuing on. 
> Sometimes there is even some other error message prior to this one. 
> Sounds like more actual debugging is needed by the programmer on this one 
> with what little information we have so far.
>
>
>
>
> ________________________________
> From: Joe Johnson <jej1216@hotmail.com>
> To: This list is for discussion about the SQR database reportinglanguage 
> from Hyperion Solutions. <sqr-users@sqrug.org>
> Sent: Monday, March 16, 2009 11:22:32 AM
> Subject: [sqr-users] Sporadic error (SQR 3301) Program stopped by user 
> request.
>
> This one is really stumping me.
>
> We have 2 PS_HOME folders, one for Production, the other for Dev/Test.
>
> An interface SQR runs successfully in PRD, and up until a specific time 
> ran successfully in TST.
> Then in TST the process errored out with the (SQR 3301) Program stopped by 
> user request. message.
> After about an hour, with no changes to the SQR, it started running to 
> success again.
>
> We have separate servers for DB, Web, Application, and Process Scheduler.
>
> Looking at all of the server logs, the only warning/error I find is in the 
> Process Scheduler logfile SCHDLR_0316.LOG:
>
> Warning:  System has detected the Process Scheduler Server is not set with 
> the required
> minimum Application Engine Tuxedo Server needed to run the maximum 
> concurrency
> based on Process Scheduler Server Setting.  It is recommended to have 
> PSAESRV
> instance in the Process Scheduler Config file set to 5. The current max
> max instance setting for the Application Engine is 3.
>
> When I check the config file, I find that PSAESRV Max Instances=5, so the 
> error is inaccurate.
>
> I had bounced the Process Scheduler earlier in an attempt to address the 
> error, but that did not correct it.
>
> Anybody know what the heck this warning means and how to fix it?
>
> TIA,
>
> Joe Johnson
>
> _______________________________________________
> sqr-users mailing list
> sqr-users@sqrug.org
> http://www.sqrug.org/mailman/listinfo/sqr-users
>
>
>
>
>
> _______________________________________________
> sqr-users mailing list
> sqr-users@sqrug.org
> http://www.sqrug.org/mailman/listinfo/sqr-users
> 

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users