Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

TWS job submit problem

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IBM Tools
View previous topic :: :: View next topic  
Author Message
Lenard Szucs

New User


Joined: 12 Sep 2013
Posts: 6
Location: Hungary

PostPosted: Fri Sep 13, 2013 5:35 pm    Post subject: TWS job submit problem
Reply with quote

Since this is my first post, I would like to say "Hi!" to everyone. icon_smile.gif

And now to my problem:
We have a small education "lpar" that runs z/OS 1.10.
The TWS version is V8R3, and we have JES2.

Just to be clear: our problem was not present until recently - everything was working fine.

When I submit a job in OPC, it never starts running, it doesn't even show up in the input queue.

The connection between the tracker and controller is OK, I can't see any problems in the MLOG, OPC recognizes JES2:

Code:
EQQZ073I OPC HAS RECOGNIZED THAT THIS IS A JES2 SYSTEM WITH     
EQQZ073I COMMAND CHARACTER $ AND THAT THE NJE NODE NAME IS N1   



The status of the job in OPC, after submiting it:
Code:

Jobname and Jobid      : TESTJOB             .ß.  .             
Reader date and time   :                                         
Status                 : Started           Job submit in progress


After a while the job ends up in the controllers EQQBRDS.

The communication between TWS and JES2 was supposed to use EXIT7 and EXIT51, which I have re-assembled, and re-linked, but that didn't help at all.

From JES2, the EXITs seem to be fine aswell:
Code:

$HASP823 EXIT(7)                                               
$HASP823 EXIT(7)    STATUS=ENABLED,ENVIRON=JES2,               
$HASP823            ROUTINES=(OPCAENT7),SPLEVEL=CHECK,TRACE=YES,
$HASP823            USECOUNT=0 

$HASP823 EXIT(51)                                               
$HASP823 EXIT(51)   STATUS=ENABLED,ENVIRON=JES2,               
$HASP823            ROUTINES=(TWSENT51),SPLEVEL=CHECK,TRACE=YES,
$HASP823            USECOUNT=0   

$HASP819 LOADMOD(OPCAXIT7)                                     
$HASP819 LOADMOD(OPCAXIT7)  ADDRESS=1E68D088,LENGTH=000428,   
$HASP819                    LOADTIME=(2013.253,13:53:33),     
$HASP819                    RMODE=ANY,SPLEVEL=CHECK,STORAGE=PVT

$HASP819 LOADMOD(TWSXIT51)                                       
$HASP819 LOADMOD(TWSXIT51)  ADDRESS=1EC2BD48,LENGTH=0002B8,     
$HASP819                    LOADTIME=(2013.253,13:53:33),       
$HASP819                    RMODE=ANY,SPLEVEL=CHECK,STORAGE=PVT                               





I even completely re-did the TWS post install customization, re-created all datasets, and that didn't help either.

I would welcome any suggestion, thanks.


edit:

This appears in the controllers MLOG:
Code:

EQQE039I LONG TIME ON INPUT QUEUE FOR JOB TESTJOB (...ß....),       
EQQE039I OPERATION(0005),                                           
EQQE039I APPL = TESTAPP         , WORKSTATION = WS01, IA = 1303121616
Back to top
View user's profile Send private message

dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Fri Sep 13, 2013 7:21 pm    Post subject:
Reply with quote

Hello and welcome to the forum,

Just wanted to say your posting style is excellent.

Unfortunately, i don't "do" tws, but sometimes a job will dissapear if there is a problem with the JOB statement . . .
Back to top
View user's profile Send private message
Lenard Szucs

New User


Joined: 12 Sep 2013
Posts: 6
Location: Hungary

PostPosted: Fri Sep 13, 2013 7:30 pm    Post subject:
Reply with quote

Thanks for the suggestion.

Just to be sure, I've reran my testjob with a full jobcard (that should 100% work), and the situation is the same...
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2422
Location: Netherlands, Amstelveen

PostPosted: Sat Sep 14, 2013 3:15 pm    Post subject:
Reply with quote

Code:

EQQE039I LONG TIME ON INPUT QUEUE FOR JOB TESTJOB (...ß....),


should be something like this :

Code:

EQQE039I LONG TIME ON INPUT QUEUE FOR JOB TESTJOB (JOB07220),


So i guess one of your JES2 exits is not working properly.
Back to top
View user's profile Send private message
Lenard Szucs

New User


Joined: 12 Sep 2013
Posts: 6
Location: Hungary

PostPosted: Mon Sep 16, 2013 12:41 pm    Post subject:
Reply with quote

Yes, that was my guess too, but when I re-assembled, relinked and reloaded both exits, nothing changed.

There was an IPL aswell - JES2 was coldstarted, and it's still not working...
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2422
Location: Netherlands, Amstelveen

PostPosted: Mon Sep 16, 2013 2:01 pm    Post subject:
Reply with quote

IIRC, there are PTF's for these exits. They were applied?
Back to top
View user's profile Send private message
Lenard Szucs

New User


Joined: 12 Sep 2013
Posts: 6
Location: Hungary

PostPosted: Mon Sep 16, 2013 2:04 pm    Post subject:
Reply with quote

Unfortunately I can't apply any PTF's on this education "LPAR" - if you know what I mean.

Btw it was working fine without the PTF's.
When I think about it, the problem started sometime after the system was stopped - when the daily plan job was still running.
Back to top
View user's profile Send private message
David Robinson

Active User


Joined: 21 Dec 2011
Posts: 175
Location: UK

PostPosted: Mon Sep 16, 2013 2:36 pm    Post subject:
Reply with quote

Is the job number displayed correctly in the event dataset (EQQEVDS)?
Back to top
View user's profile Send private message
Lenard Szucs

New User


Joined: 12 Sep 2013
Posts: 6
Location: Hungary

PostPosted: Mon Sep 16, 2013 2:43 pm    Post subject:
Reply with quote

No, it's wrong there too:

Code:

IJ1 WS01TESTAPP         1303121616......TESTJOB ...ß.....ĚY....?.<<.OPCC....EQQG
Back to top
View user's profile Send private message
David Robinson

Active User


Joined: 21 Dec 2011
Posts: 175
Location: UK

PostPosted: Mon Sep 16, 2013 5:06 pm    Post subject:
Reply with quote

Very odd. One for IBM I would have thought. Although I think v8.3 may now be out of support.
Back to top
View user's profile Send private message
Lenard Szucs

New User


Joined: 12 Sep 2013
Posts: 6
Location: Hungary

PostPosted: Mon Sep 16, 2013 5:08 pm    Post subject:
Reply with quote

Well, going to IBM is not an option ;)
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IBM Tools All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Problem in writing Output file vickey_dw COBOL Programming 5 Mon Nov 14, 2016 11:14 pm
No new posts Problem in Running Query via JCL vickey_dw DB2 3 Tue Oct 18, 2016 11:11 pm
No new posts DB2 Streaming Batch Processing Problem Manshadi DB2 4 Sat Sep 24, 2016 12:14 pm
No new posts Problem with GETMAIN command amitc23 CICS 6 Thu Sep 01, 2016 1:01 pm
No new posts TXT2PDF problem - printing @ in PDF vipul65 All Other Mainframe Topics 9 Thu Aug 25, 2016 12:48 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us