Author Topic: JES data disappeared  (Read 3758 times)

LWagner

  • Guest
JES data disappeared
« on: December 09, 2011, 06:40:08 PM »
I have many application that load to CMOD via the JES queue and ARSLOAD started task.  The code below worked to load the dataset named.  But when it ran as part of its native PROC, CMOD got nothing.  No load, no error, and no data set remaining in the SDSF Output queue.  It ran every day since June, no problem.  There was an extra run last Sunday, which had the same problem as this. It has stopped loading sinec last Sunday. But this code runs fine submitted by itself.

Interesting mystery ?  Not RACF, since the  same id runs another 100+ procs daily, and loads reports to CMOD. Nothing else missing.

//CMOD84LD EXEC PGM=IEBGENER             
//SYSUT1   DD  DISP=OLD,DSN=$CI.R11BC26   
//SYSUT2   DD  SYSOUT=(I,RP11)           
//SYSPRINT DD  SYSOUT=*                   
//SYSIN    DD  DUMMY

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1202
    • View Profile
Re: JES data disappeared
« Reply #1 on: December 12, 2011, 10:45:13 AM »
Larry, just a wild guess, but you wouldn't have to do a FREE=CLOSE on that output, would you?
#zOS #ODF

LWagner

  • Guest
Re: JES data disappeared
« Reply #2 on: December 12, 2011, 11:11:05 AM »
Ed,

The programmer confirmed there was no change in the proc. Never required that step before.

LWagner

  • Guest
Re: JES data disappeared
« Reply #3 on: December 20, 2011, 11:28:18 AM »
Ed:

Where would that FREE=CLOSE be ?

When other reports fail to load, they stay on the JES queue.

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1202
    • View Profile
Re: JES data disappeared
« Reply #4 on: December 21, 2011, 07:55:15 AM »
On the SYSUT2 statement? 

Mind you, Larry, this really is just wild guessing.
#zOS #ODF

LWagner

  • Guest
Re: JES data disappeared
« Reply #5 on: December 21, 2011, 07:57:51 AM »
Wild but related guesses can be the only solutions sometimes.

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1202
    • View Profile
Re: JES data disappeared
« Reply #6 on: December 22, 2011, 11:39:51 AM »
Larry - I know the description doesn't match, but do you have PM46856 on your system? 

If you're still having the problem, try rolling out that fix and see if it makes a difference.

Ed
#zOS #ODF