OnDemand Users Group

Support Forums => CMOD for z/OS Server => Topic started by: LWagner on December 10, 2011, 01:40:08 AM

Title: JES data disappeared
Post by: LWagner on December 10, 2011, 01:40:08 AM
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
Title: Re: JES data disappeared
Post by: Ed_Arnold on December 12, 2011, 05:45:13 PM
Larry, just a wild guess, but you wouldn't have to do a FREE=CLOSE on that output, would you?
Title: Re: JES data disappeared
Post by: LWagner on December 12, 2011, 06:11:05 PM
Ed,

The programmer confirmed there was no change in the proc. Never required that step before.
Title: Re: JES data disappeared
Post by: LWagner on December 20, 2011, 06:28:18 PM
Ed:

Where would that FREE=CLOSE be ?

When other reports fail to load, they stay on the JES queue.
Title: Re: JES data disappeared
Post by: Ed_Arnold on December 21, 2011, 02:55:15 PM
On the SYSUT2 statement? 

Mind you, Larry, this really is just wild guessing.
Title: Re: JES data disappeared
Post by: LWagner on December 21, 2011, 02:57:51 PM
Wild but related guesses can be the only solutions sometimes.
Title: Re: JES data disappeared
Post by: Ed_Arnold on December 22, 2011, 06:39:51 PM
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