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
 

 

EZACFSM1 Won't Write to INTRDR?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics
View previous topic :: :: View next topic  
Author Message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Wed Feb 17, 2010 1:09 am    Post subject: EZACFSM1 Won't Write to INTRDR?
Reply with quote

One of my kouhai asked for help with the following JCL:
Code:
//CURDATE JOB ,'RUNJCL',CLASS=F,MSGCLASS=1,   
//         NOTIFY=&SYSUID,REGION=4096K       
//STEP00   EXEC PGM=EZACFSM1                 
//SYSIN    DD DATA,DLM=@@                     
//MEEBDATE JOB ,'RUNJCL',CLASS=F,MSGCLASS=1, 
//         NOTIFY=&SYSUID,REGION=4096K       
//STEP01   EXEC PGM=IEFBR14                   
//SYSUT2   DD  DSN=MEEB.WORK.D&LYYMMDD,       
//             DISP=(NEW,CATLG,DELETE),       
//             UNIT=SYSDA,RECFM=FB,LRECL=80, 
//             SPACE=(CYL,(1,1),RLSE)         
@@                                           
//SYSOUT   DD SYSOUT=(*,INTRDR)               

He couldn't get EZACFSM1 to write to SYSOUT. Neither could I...if it were defined as SYSOUT=(*,INTRDR). Anything else, no problem. However, the following JCL did achieve the desired effect:
Code:
//SHGBD1   JOB ,'RUNJCL',CLASS=F,MSGCLASS=1,                       
//         NOTIFY=&SYSUID,REGION=4096K                             
//STEP00   EXEC PGM=EZACFSM1                                       
//SYSPRINT DD SYSOUT=*                                             
//SYSIN    DD DATA,DLM=@@                                           
//SHGBD2   JOB ,'RUNJCL',CLASS=F,MSGCLASS=1,                       
//         NOTIFY=&SYSUID,REGION=4096K                             
//STEP01   EXEC PGM=IEFBR14                                         
//SYSUT2   DD  DSN=SHGB.WORK.D&LYYMMDD,                             
//             DISP=(NEW,CATLG,DELETE),                             
//             UNIT=SYSDA,RECFM=FB,LRECL=80,                       
//             SPACE=(CYL,(1,1),RLSE)                               
@@                                                                 
//SYSOUT   DD DSN=&&FOO,DISP=(NEW,PASS),SPACE=(TRK,1),UNIT=TEMPDISK,
//         DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)                       
//STEP02   EXEC PGM=IEBGENER                                       
//SYSPRINT DD   SYSOUT=*                                           
//SYSIN    DD   DUMMY                                               
//SYSUT1   DD   DSN=&&FOO,DISP=(OLD,DELETE)                         
//SYSUT2   DD   SYSOUT=(*,INTRDR)                                 

Has anyone seen a similar phenomenon? A locally-defined exit, or even a zap?
Back to top
View user's profile Send private message

superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4648
Location: Raleigh, NC, USA

PostPosted: Wed Feb 17, 2010 1:24 am    Post subject: Reply to: EZACFSM1 Won't Write to INTRDR?
Reply with quote

I need to include the two statements RECFM=FB and LRECL=254 for the //SYSOUT DD statement.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Wed Feb 17, 2010 1:28 am    Post subject:
Reply with quote

Have you tried
Code:
//CURDATE JOB ,'RUNJCL',CLASS=F,MSGCLASS=1,   
//         NOTIFY=&SYSUID,REGION=4096K       
//STEP00   EXEC PGM=EZACFSM1                 
//SYSIN    DD DATA,DLM=@@                     
//MEEBDATE JOB ,'RUNJCL',CLASS=F,MSGCLASS=1,
//         NOTIFY=&SYSUID,REGION=4096K       
//STEP01   EXEC PGM=IEFBR14                   
//SYSUT2   DD  DSN=MEEB.WORK.D&LYYMMDD,       
//             DISP=(NEW,CATLG,DELETE),       
//             UNIT=SYSDA,RECFM=FB,LRECL=80,
//             SPACE=(CYL,(1,1),RLSE)         
@@                                           
//SYSOUT   DD SYSOUT=(*,INTRDR),LRECL=80,BLKSIZE=80,BUFNO=1,RECFM=F     
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Wed Feb 17, 2010 1:28 am    Post subject:
Reply with quote

Hmmm, now that you mention the subject, wouldn't the DCB for a file defined as SYSOUT=* be RECFM=FBA,LRECL=133? That might cause INTRDR to choke, perhaps?
Back to top
View user's profile Send private message
Bill Dennis

Active Member


Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA

PostPosted: Wed Feb 17, 2010 2:52 am    Post subject:
Reply with quote

SYSOUT is not always a "report" file. This case of SYSOUT is simply the OUT copy of the IN file.

BTW, my JCL works correctly without any DCB info on SYSOUT.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Wed Feb 17, 2010 3:12 am    Post subject:
Reply with quote

Bill, are you on a JES3 system?
Back to top
View user's profile Send private message
gcicchet

Senior Member


Joined: 28 Jul 2006
Posts: 1703
Location: Australia

PostPosted: Wed Feb 17, 2010 3:16 am    Post subject:
Reply with quote

Hi,

mine works fine too without DCB information (JES2)


Gerry
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Wed Feb 17, 2010 3:07 pm    Post subject:
Reply with quote

gcicchet wrote:
mine works fine too without DCB information (JES2)
Ditto.
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10202
Location: italy

PostPosted: Wed Feb 17, 2010 3:14 pm    Post subject: Reply to: EZACFSM1 Won't Write to INTRDR?
Reply with quote

Quote:
//SYSOUT DD SYSOUT=(*,INTRDR)


looks odd that the second time worked
the sysout=* construct puts things in the same sysout class as the msgclass!
and thats usually a <printer> thing

the traditional class for <punched> things is B

but there would be the need of some testing to find out|
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Wed Feb 17, 2010 3:19 pm    Post subject:
Reply with quote

ok, I tried with with/without DCB parametes - both work for me. However, when you say
Quote:
He couldn't get EZACFSM1 to write to SYSOUT. Neither could I...if it were defined as SYSOUT=(*,INTRDR).
what exactly happend?
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Wed Feb 17, 2010 4:45 pm    Post subject:
Reply with quote

Anuj Dhawan wrote:
ok, I tried with with/without DCB parametes - both work for me. However, when you say
Quote:
He couldn't get EZACFSM1 to write to SYSOUT. Neither could I...if it were defined as SYSOUT=(*,INTRDR).
what exactly happend?

As far as I could tell, nothing. The JCL was not submitted, and there were no EXCPs for SYSOUT in the system messages. To the left, when I defined the DD as SYSOUT=* or as DSN=..., the JCL appeared in sysout or the data set, and there were two EXCPs to SYSOUT.

enrico-sorichetti wrote:
the traditional class for <punched> things is B

but there would be the need of some testing to find out|

I'll have to review the standard sysout class documentation when my office opens up in a couple of hours, but I'm 99% sure that sysout class B has been redefined to mean some sort of letterhead.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Wed Feb 17, 2010 4:59 pm    Post subject:
Reply with quote

What about RACF or system exits to deny the use of using INTRDR ?
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Wed Feb 17, 2010 8:22 pm    Post subject:
Reply with quote

expat wrote:
What about RACF or system exits to deny the use of using INTRDR ?

That was what I was thinking, although I was not sure if they could detect that the write to INTRDR was coming from EZACFSM1 vs. IEBGENER, which would be necessary for the situation to have been true.
===
I think that the responses from various members that the original JCL does/does not work for them without DCB parameters indicates that there is enough variation in installations that this behavior, although surprising, should not be wholly unexpected. Thank you all for your efforts in this matter.
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 -> All Other Mainframe Topics All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Error IEC161I 052(009,XXXRS00)-084 wh... amitc23 JCL & VSAM 10 Wed Oct 12, 2016 5:00 pm
No new posts how to DYNAMICALLY write sort cond to... mohamedmubee COBOL Programming 13 Fri Aug 26, 2016 11:46 pm
No new posts Compare 2 files & write Indicator... nagendrapgupta SYNCSORT 5 Sun May 15, 2016 10:42 am
No new posts DFSORT to match two files and write John F Dutcher DFSORT/ICETOOL 6 Thu May 12, 2016 5:17 pm
No new posts Write a job to delete the files aging... Abhinav Roy JCL & VSAM 4 Fri Dec 18, 2015 7:17 pm


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