Unable to get Sysout

Post Reply
User avatar
dbeardking
Nouveau
Nouveau
Posts: 12
Joined: 02 Jul 2009 12:00

Unable to get Sysout

Post by dbeardking » 02 Jul 2009 5:13

Sometimes when a job fails, I am unable to retrieve the Sysout. When I try to open the Sysout, I get the following message: 'Request rejected by datacenter'. The same happens when I try pulling the sysout after a while. Could someone throw some light ?

User avatar
GNappo
Nouveau
Nouveau
Posts: 70
Joined: 03 Sep 2007 12:00
Location: Italy

Post by GNappo » 02 Jul 2009 9:10

Hi dbeardking,

probably the job don't generate a sysout, try to see the log of the job.

If logs don't solve your problem, please let me know:

- Control-M Server Version and Server OS
- Control-M Agent Version, Fix-Pack and Server OS
- Job type

Best Regards

Giuseppe

User avatar
rahulsehgal
Nouveau
Nouveau
Posts: 148
Joined: 19 Mar 2009 12:00
Location: Delhi
Contact:

Post by rahulsehgal » 03 Jul 2009 5:06

Hi,

Are you receiving this type of error

"Message from CONTROL-M: PLNSHCTM01
Action : 'Get job's sysout list'
Job : 'BVF0004D'

Request rejected by Data Center
CTM5319 SYSOUT DOES NOT EXIST FOR THIS JOB"

If so, then this means that the job has not generated any Sysout.
This may happen because the job has failed due to some Server Failue or some Unknown failure and was unable to run any process or command.

hipikll

Post by hipikll » 04 Jul 2009 7:23

It happens mainly, when job was unable to be executed. So there is no sysout as there is nothing to show. Just log :)

User avatar
Walty
Nouveau
Nouveau
Posts: 473
Joined: 20 Jan 2006 12:00

Post by Walty » 06 Jul 2009 9:03

Hi,

Do you have run job outside Control-M ?
Have you one sysout in this case ?
Best regards
Walty

User avatar
JoPoCME
Nouveau
Nouveau
Posts: 35
Joined: 23 Oct 2008 12:00
Location: Miami, Florida

Post by JoPoCME » 09 Jul 2009 2:21

I've had this issue a few times due to authorizations in regards to AFT. Since the job is never allowed to begin there is no sysoutj. Verify that your job is authorized to access the server(s) it is trying to run on.

Here is a link to a post where an odd COMPSTAT and no sysout were an issue with the Enterprise.

https://www.scheduler-usage.com/viewtopic.php?t=1192

User avatar
dbeardking
Nouveau
Nouveau
Posts: 12
Joined: 02 Jul 2009 12:00

Post by dbeardking » 13 Jul 2009 1:54

Thank you guys for all the info.

Post Reply