Quantcast
Channel: IBM Mainframe Computers Forums
Viewing all 8500 articles
Browse latest View live

All Other Mainframe Topics :: RE: Hercules: The compile JCL always picks up the old Program

$
0
0
Author: sandeep kumar302
Posted: Fri Apr 27, 2018 7:57 pm (GMT 5.5)

Is there anything wrong in my compile JCL or I need to do some changes to IGYWCL Procedure.
_________________
Making Mainframe simple


All Other Mainframe Topics :: RE: Hercules: The compile JCL always picks up the old Program

$
0
0
Author: sandeep kumar302
Posted: Fri Apr 27, 2018 7:58 pm (GMT 5.5)

Can a moderator please change the subject name to 'What is the fix for compile JCL error -INVALID RECFM FOR DDNAME ddname AND CONCATENATION NUMBER number.'
_________________
Making Mainframe simple

All Other Mainframe Topics :: RE: Hercules: The compile JCL always picks up the old Program

$
0
0
Author: enrico-sorichetti
Subject: Reply to: Hercules: The compile JCL always picks up the old Program
Posted: Fri Apr 27, 2018 8:03 pm (GMT 5.5)

what happened when You googled with IEW2730S ?
the explanation in the manual is pretty clear

anyway the action is to fix the dcb attributes of the dataset
_________________
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort icon_cool.gif

All Other Mainframe Topics :: RE: Hercules: The compile JCL always picks up the old Program

$
0
0
Author: sandeep kumar302
Posted: Fri Apr 27, 2018 8:07 pm (GMT 5.5)

Hi Enrico,

This is fixed now. I changed my compile JCL. The corrected compile JCL is below -

Code:

//COMPJCL6 JOB 1AD40G12,'COMPCOB-COMPLINK',NOTIFY=&SYSUID       
//*************************************************************
//*COMPILAR Y LINKEDITAR                                       
//*************************************************************
//STEP0      EXEC IGYWCL,PARM.COBOL='LIB,APOST,XREF,MAP,OFFSET'
//* -----------------------------------------------------------
//*         JCL PARA COMPILAR PGM DE COBOL (SIN DB2 Y SIN CICS)
//* -----------------------------------------------------------
//* -----------------------------------------------------------
//COBOL.SYSLIB DD DISP=SHR,DSN=SANDY.COBOL.COPYLIB             
//COBOL.SYSIN  DD DISP=SHR,DSN=SANDY.COBOL.SRCLIB(COB002)       
//LKED.SYSLMOD DD DISP=OLD,DSN=SANDY.COBOL.LOADLIB(COB002)     
/*                                                             
//                                                             

_________________
Making Mainframe simple

All Other Mainframe Topics :: RE: INVALID RECFM FOR DDNAME SYSLIN AND CONCATENATION NUMBER 2.

$
0
0
Author: sergeyken
Subject: Re: INVALID RECFM FOR DDNAME SYSLIN AND CONCATENATION NUMBER
Posted: Fri Apr 27, 2018 11:52 pm (GMT 5.5)

sandeep kumar302 wrote:

Code:

........
//LKED.SYSIN  DD                                               
  NAME COB002(R)                                               
/*                                                             


Code:

........
//LKED   EXEC PGM=HEWL,COND=(8,LT,COBOL),REGION=0M
.........
//SYSLIN   DD  DSNAME=&&LOADSET,DISP=(OLD,DELETE)
//         DD  DDNAME=SYSIN                       


The used form of this statement
//LKED.SYSIN DD
is nothing else but EMPTY DD STATEMENT, with NO PARAMETERS DEFINED. This bug is causing the error
INVALID RECFM FOR DDNAME SYSLIN CONCATENATION NUMBER 2
because within the JCL PROC this //SYSIN is concatenated under //SYSLIN, with number 2.
_________________
Tyrannosaurus-REXX

SYNCSORT :: RE: OUTREC OVERLAY different to INCREC generated INPUT

$
0
0
Author: sergeyken
Posted: Fri Apr 27, 2018 11:56 pm (GMT 5.5)

Joerg.Findeisen wrote:
Thanks for replying back and the hints for coding. I am so used to that sequence that I had forgotten to rearrange it prior to posting. icon_redface.gif


I cannot run this test by myself right now, but you continuously refuse to provide THE REQUIRED INFO IN FULL.

Sorry, in this case I cannot help.
_________________
Tyrannosaurus-REXX

COBOL Programming :: LE Modules in Link Edit

$
0
0
Author: John Poulakos
Subject: LE Modules in Link Edit
Posted: Sat Apr 28, 2018 12:14 am (GMT 5.5)

I'm not sure this is the place to ask, but here goes:

If I compile and link a new COBOL program that doesn't call any old modules I am picking up LE modules (CEExxxxx) from 2013. However, if I compile an older COBOL program, that calls old COBOL modules, I get LE modules that are much older. It's like the compiled program inherits the LE modules from the oldest module it calls.

It doesn't seem to hurt anything. I was just curious.

DB2 :: RE: Remove all Parenthetical Statements - including the parent

$
0
0
Author: Rohit Umarjikar
Posted: Sat Apr 28, 2018 2:19 am (GMT 5.5)

Is this a single occurrence or multiples for a a single row?
_________________
Regards,
Rohit Umarjikar
A leader is one who knows the way, goes the way, and shows the way.


All Other Mainframe Topics :: RE: INVALID RECFM FOR DDNAME SYSLIN AND CONCATENATION NUMBER 2.

$
0
0
Author: sandeep kumar302
Subject: Re: INVALID RECFM FOR DDNAME SYSLIN AND CONCATENATION NUMBER
Posted: Sat Apr 28, 2018 9:29 am (GMT 5.5)

Hi Sergeyken,
Yes, that's right. Thanks anyways.

Quote:

The used form of this statement
//LKED.SYSIN DD
is nothing else but EMPTY DD STATEMENT, with NO PARAMETERS DEFINED. This bug is causing the error
INVALID RECFM FOR DDNAME SYSLIN CONCATENATION NUMBER 2
because within the JCL PROC this //SYSIN is concatenated under //SYSLIN, with number 2.



and the issue is fixed.
_________________
Making Mainframe simple

DB2 :: RE: Need suggestion on how to force referential integrity

$
0
0
Author: subratarec
Posted: Sat Apr 28, 2018 2:15 pm (GMT 5.5)

Hi Rohit,

Your question is absolutely correct and the answer is 'yes' they have!. But the main issue is currently we were informed that our DBAs are very short handed so for our new project what we are doing is we are creating what all we can and understand from our end.

I wanted to make sure if my idea towards above subject is correct. We have create our compete data dictionary on our own in Excel and gave that to our DBA I guess they will pass the date to Powerbuilder tool to generate table design.

TSO/ISPF :: RE: how to display APL characters?

$
0
0
Author: Steve Coalbran
Posted: Sat Apr 28, 2018 5:24 pm (GMT 5.5)

prino wrote:
A bit of REXX...
Hej Robert,
I recently wrote something remarkably similar.
The displays (attached) toggle using the GE command or one can specifically issue GE OFF, GE ON, TEXT ON, TEXT OFF.
Petty much written for educational purposes but I use it a lot nowadays.
It took me a while to get used to Graphic Escape chars. I have to admit I had help from Marvin Knight in Raleigh to start with and it was only recently I was given the requirement to use them!

TSO/ISPF :: RE: how to display APL characters?

$
0
0
Author: Steve Coalbran
Subject: Problem with the PREVIEW with attachments?
Posted: Sat Apr 28, 2018 5:28 pm (GMT 5.5)

This looks OK when I SUBMIT it but when I PREVIEW it I see the first attached Attachment twice!
Technical problem?

JCL & VSAM :: RE: Job monitoring request

$
0
0
Author: Steve Coalbran
Subject: Job monitoring request + to send an email
Posted: Sat Apr 28, 2018 6:20 pm (GMT 5.5)

Job Monitoring Request:
We use TWS (alias OPC) to schedule jobs, in Sweden we have some 71000 jobs.
I have also used JOBGROUPs successfully on a much smaller scale.
Checkout the SCHEDULE statement as well, you could write a self-resceduling job using HOLDUNTL to run at a certain periodicity.

Sending Email:
We use a program called MEMOAPIX. Another one is MEMOAPI. These can send memos with attachments if necessary.
One could wait for z/OS 2.3 which I see will have EMAIL options on a NOTIFY, Can be useful? Sadly we are still on 2.2. icon_sad.gif

/Steve

CLIST & REXX :: RE: How to list data set names with different HLQ?

$
0
0
Author: Steve Coalbran
Subject: How to list data set names with different LLQ?
Posted: Sat Apr 28, 2018 7:45 pm (GMT 5.5)

daveporcelan wrote:
Nic,
I am NOT missing - last_nodes.0 = 3
I leave it off on purpose. My method allows adding more entries without having to set this value as well. I have been burned in the past.
I quite like it.
Alternative solution: Read the list of LLQ specifications?
Code:
"EXECIO * DISKR SYSIN (STEM last_nodes. FINIS "
and
Code:
//SYSIN   *
IS%A*
IF%B*X
IB%88*
/*
By this means one can use full member patterns?
This also sets last_nodes.0?
_________________
/Steve

CLIST & REXX :: RE: How to list data set names with different HLQ?

$
0
0
Author: Willy Jensen
Posted: Sun Apr 29, 2018 2:44 pm (GMT 5.5)

my personal preference for small lists is using a string, like:
Code:
 list='item1 item2 item3'     
 do listn=1 to words(list)   
   call sub(word(list,listn))
 end 

_________________
WJ


SYNCSORT :: RE: OUTREC OVERLAY different to INCREC generated INPUT

$
0
0
Author: Joerg.Findeisen
Posted: Sun Apr 29, 2018 4:49 pm (GMT 5.5)

Sorry for the delayed response. It's a weekend before a bank holiday here and I am On-call. icon_confused.gif

@Arun: Yes, your assumption is correct. SYNCSORT does give me a different result compared to DFSORT when I use in the OUTREC the following statement:

Code:
OUTREC IFTHEN=(WHEN=INIT,OVERLAY=(121:+0,TO=ZD,LENGTH=4))

To me it should provide exactly the same result as when using:
Code:
OUTREC OVERLAY=(121:+0,TO=ZD,LENGTH=4)


To summarize this, DFSORT provides same result for both variants in the OUTREC statement while SYNCSORT fails using IFTHEN OVERLAY in my OUTREC.

@sergeyken: Hope I could make the issue more clear now. Sorry for the confusion if any.

Initial question of mine was if I am doing something wrong for SYNCSORT or if it is a bug in the Software. Presently I am guessing my coding is correct.

Cheers,
Joerg

SYNCSORT :: RE: OUTREC OVERLAY different to INCREC generated INPUT

$
0
0
Author: Joerg.Findeisen
Posted: Sun Apr 29, 2018 9:24 pm (GMT 5.5)

Code:
//PARSE    EXEC PGM=SORT,PARM='MSG=AP'                               
//SYSOUT   DD SYSOUT=*                                                 
//SORTIN   DD DISP=SHR,DSN=&SYSUID..SYSPRINT                           
//SORTOUT  DD SYSOUT=*,LRECL=170                                       
//SYSIN    DD *                                                         
  OPTION VLSCMP                                                         
  SORT FIELDS=(6,44,CH,D)                                               
  INCLUDE COND=((6,15,SS,EQ,C'GDG BASE ------,NONVSAM -------'),OR,     
                 42,16,CH,EQ,C'CREATION--------')                       
  INREC IFTHEN=(WHEN=GROUP,                                             
    BEGIN=(6,15,SS,EQ,C'GDG BASE ------,NONVSAM -------'),             
    PUSH=(126:22,44)),                                                 
    IFTHEN=(WHEN=(42,16,CH,EQ,C'CREATION--------'),                     
      BUILD=(1,4,C'?',126,44,X,58,8,UFF,M11,LENGTH=7,DATE3),HIT=NEXT),
    IFTHEN=(WHEN=(5,1,CH,EQ,C'?'),                                     
      PARSE=(%00=(STARTAFT=C'.PDUMP.',ENDBEFR=C'.',FIXLEN=1)),         
      OVERLAY=(50:%00,65:6,44,JFY=(SHIFT=RIGHT),                       
               65:65,35,JFY=(SHIFT=LEFT)),HIT=NEXT),                   
    IFTHEN=(WHEN=(101,1,CH,EQ,C'G',AND,                                 
                 (102,4,ZD,GE,+0,AND,102,4,ZD,LE,+9999),AND,           
                  106,1,CH,EQ,C'V',AND,107,2,ZD,EQ,+0),                 
      BUILD=(1,4,C'Z',6,44,50,1,51,7,58,7,                             
             58,7,Y4T,DATEDIFF,51,7,Y4T,65,35,9X)),                     
    IFTHEN=(WHEN=(5,1,CH,EQ,C'?'),                                     
      BUILD=(1,4,C'?',6,44,50,1,51,7,58,7,                             
             58,7,Y4T,DATEDIFF,51,7,Y4T,6,44))                         
  OUTREC IFTHEN=(WHEN=INIT,OVERLAY=(121:+0,TO=ZD,LENGTH=4))             
  END


is different in DFSORT and SYNCSORT,while

Code:
//PARSE    EXEC PGM=SORT,PARM='MSG=AP'                               
//SYSOUT   DD SYSOUT=*                                                 
//SORTIN   DD DISP=SHR,DSN=&SYSUID..SYSPRINT                           
//SORTOUT  DD SYSOUT=*,LRECL=170                                       
//SYSIN    DD *                                                         
  OPTION VLSCMP                                                         
  SORT FIELDS=(6,44,CH,D)                                               
  INCLUDE COND=((6,15,SS,EQ,C'GDG BASE ------,NONVSAM -------'),OR,     
                 42,16,CH,EQ,C'CREATION--------')                       
  INREC IFTHEN=(WHEN=GROUP,                                             
    BEGIN=(6,15,SS,EQ,C'GDG BASE ------,NONVSAM -------'),             
    PUSH=(126:22,44)),                                                 
    IFTHEN=(WHEN=(42,16,CH,EQ,C'CREATION--------'),                     
      BUILD=(1,4,C'?',126,44,X,58,8,UFF,M11,LENGTH=7,DATE3),HIT=NEXT),
    IFTHEN=(WHEN=(5,1,CH,EQ,C'?'),                                     
      PARSE=(%00=(STARTAFT=C'.PDUMP.',ENDBEFR=C'.',FIXLEN=1)),         
      OVERLAY=(50:%00,65:6,44,JFY=(SHIFT=RIGHT),                       
               65:65,35,JFY=(SHIFT=LEFT)),HIT=NEXT),                   
    IFTHEN=(WHEN=(101,1,CH,EQ,C'G',AND,                                 
                 (102,4,ZD,GE,+0,AND,102,4,ZD,LE,+9999),AND,           
                  106,1,CH,EQ,C'V',AND,107,2,ZD,EQ,+0),                 
      BUILD=(1,4,C'Z',6,44,50,1,51,7,58,7,                             
             58,7,Y4T,DATEDIFF,51,7,Y4T,65,35,9X)),                     
    IFTHEN=(WHEN=(5,1,CH,EQ,C'?'),                                     
      BUILD=(1,4,C'?',6,44,50,1,51,7,58,7,                             
             58,7,Y4T,DATEDIFF,51,7,Y4T,6,44))                         
  OUTREC OVERLAY=(121:+0,TO=ZD,LENGTH=4)             
  END


produces the same output in both products. As stated, there are a few more IFTHEN in my OUTREC (which I haven't posted yet) to be applied so I wish to see the same result with IFTHEN at first. Sometimes SYNCSORT is more strict with Syntax and it puzzles me why I see different results.

SYNCSORT :: RE: OUTREC OVERLAY different to INCREC generated INPUT

$
0
0
Author: Joerg.Findeisen
Posted: Sun Apr 29, 2018 9:40 pm (GMT 5.5)

The code shall be used to find expired DFDSS backups which by identifier can be either Daily, Weekly or Monthly and have a creation date that exceeds a certain value (hence the IDCAMS input).
If all GDS have been expired also the associated empty GDG base with no active GDS has to be deleted.

With the supplied code, SYNCSORT would provide me with DELETE statements for the latest active GDS which is not correct.

Most of my installations do have in fact DFSORT which never lets me down, but out of curiosity I'd like to see it working also with SYNCSORT.

Cheers,
Joerg

SYNCSORT :: RE: OUTREC OVERLAY different to INCREC generated INPUT

$
0
0
Author: Joerg.Findeisen
Posted: Mon Apr 30, 2018 5:58 am (GMT 5.5)

If it might be of interest, the SYNCSORT level used identifies itself with:

WER169I RELEASE 2.1 BATCH 0539 TPF LEVEL 1.1

COBOL Programming :: RE: LE Modules in Link Edit

$
0
0
Author: Garry Carroll
Posted: Mon Apr 30, 2018 5:11 pm (GMT 5.5)

If sub-modules are link-edited without specifying NCAL, they will resolve any modules (including LE ones) that are called by them. This can result in multiple copies of (e.g.) LE modules being included in the final load module, only one of which is used to resolve all references. Which copy is used is unpredictable without specifying via control cards.

Garry.
_________________
Everyone's entitled to ONE fatal mistake.....

Viewing all 8500 articles
Browse latest View live