View previous topic :: View next topic
|
Author |
Message |
Poha Eater
New User
Joined: 31 Aug 2016 Posts: 74 Location: India
|
|
|
|
Hi,
I have 2 Input files (say..F1 & F2). I am trying to copy matching data from File 1 & 2 based on the key and trying to override the data in File 1 from the data of File 2 when the keys are matching and also keeping the original data of File 1 when the keys are not matching.
This is the SORT card which i created :
Code: |
//STEP03 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//SORTJNF1 DD DSN=T906.TEST.QUIZ015.FILE1,DISP=SHR
//SORTJNF2 DD DSN=T906.TEST.QUIZ015.FILE2,DISP=SHR
//SORTOUT DD DSN=T906.TEST.QUIZ015.OUTFILE,DISP=(NEW,CATLG,DELETE),
// DCB=(LRECL=80,RECFM=FB,BLKSIZE=0)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
OPTION COPY
JOINKEYS F1=SORTJNF1,FIELDS=(01,7,A,81,12,A)
JOINKEYS F2=SORTJNF2,FIELDS=(01,7,A,81,12,A)
JOIN UNPAIRED,F1
REFORMAT FIELDS=(F1:1,80,?,F2:1,12)
INREC IFOUTLEN=80,
IFTHEN=(WHEN=(81,1,CH,EQ,C'B'),OVERLAY=(10:82,12))
/*
|
But when i am doing jcl scan to check any error. This is the error i am getting :
Code: |
SEV MSG NO. MESSAGE TEXT
-----------------------------------------------------
E1 8 DSS10065E PARAMETER 'F1' IS UNIDENTIFIED.
E2 8 DSS10065E PARAMETER 'F2' IS UNIDENTIFIED.
|
I have never seen this error before while using SORT JOIN. I have also searched for this error but have not found anything regarding this error. So could someone please point it out what i am missing here. |
|
Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006 Posts: 1193 Location: Dublin, Ireland
|
|
|
|
There's no F1 or F2 parameter in any of your JCL. Your scan may be trying to check your SORT control cards.
Garry |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
that' s NOT a jcl error,
the jcl checker used is not worth the money Your organisation pays
search the forum and You will see that the F1 and F2 specifications are right, or ...
RTFM
from the dfsort smarts tricks
Code: |
//JK1 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//IN1 DD DSN=... file 1
//IN2 DD DSN=... file 2
//OUT DD DSN=... output file
//SYSIN DD *
JOINKEYS F1=IN1,FIELDS=(1,3,A),SORTED
JOINKEYS F2=IN2,FIELDS=(1,3,A),SORTED
REFORMAT FIELDS=(F1:1,9,F2:5,5)
OPTION COPY
OUTFIL FNAMES=OUT,BUILD=(1,9,X,10,5) |
|
|
Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013 Posts: 917 Location: The Universe
|
|
|
|
Poha Eater wrote: |
...
Code: |
SEV MSG NO. MESSAGE TEXT
-----------------------------------------------------
E1 8 DSS10065E PARAMETER 'F1' IS UNIDENTIFIED.
E2 8 DSS10065E PARAMETER 'F2' IS UNIDENTIFIED.
|
|
This is not an IBM error. It is an error from your JCL checker. See if you can find the error in your JCL checker documentation. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
Quote: |
This is not an IBM error. It is an error from your JCL checker. See if you can find the error in your JCL checker documentation.
|
it is NOT even an error , if You trust the various example posted by Frank Yaeger
It is an error OF the JCL checker.
most jcl checkers give false positives on the various utility control statements |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3053 Location: NYC,USA
|
|
|
|
Try mapping it this way instead of what you did and if you still get the same issue then test the SORT CARD bypassing the JCL SCAN and report that SCAN issue to the right team to fix it.
Code: |
JOINKEYS FILE=F1
JOINKEYS FILE=F2 |
|
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
why keeping beating a dead horse ...
from a dfsort perspective there is nothing wrong with the control statement
jcl checker positives should be filtered by good judgement and experience |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3053 Location: NYC,USA
|
|
|
|
I have suggested what manual says about how to use JOINKEYS STATEMENT when datasets DD NAMEs are defined with SORTJNF1 and SORTJNF2.
You might be right but I still believe it’s worth of try before assuming anything is dead. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3053 Location: NYC,USA
|
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
I said NOTHING about You being wrong ...
I was ONLY and ONLY considering and commenting about
the false positive as reported from the jcl checker
and the manual
PS ...
on a forum generally the sentences like
see here for the syntax of the joinkey statement
- and a link -
are addressed to the TS |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3053 Location: NYC,USA
|
|
|
|
It is clearly stated how JOINKEYS DD NAMES are to be referenced. It is said that if you are using SORTJNF1/F2 then JOINKEYS statements has to be followed by FILE=1/2 or FILES=1/2 and any other ddname is used instead of SORTJNF1/2 but that should be followed by F1/F2= ddname.
www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.icea100/ice2ca_JCL_for_a_JOINKEYS_application.htm
Also, if you think F1=SORTJNF1 use is allowed (because directly it’s not said not allowed) then JCL SCAN is wrong as outlined by you otherwise No. So TS needs to test the jcl first and update us. |
|
Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008 Posts: 2023 Location: USA
|
|
|
|
Initially all SORT utilities accepted only one format:
Code: |
JOINKEYS FILE=F1
JOINKEYS FILE=F2
|
Once upon a time new format had been introduced in one of updated SORT version:
Code: |
JOINKEYS F1=ddname1
JOINKEYS F2=ddname2
|
The updated version(s) of SORT do accept both formats, while the older versions accept only the original one. |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3053 Location: NYC,USA
|
|
|
|
By now we and TS as well known that JOINKEYS F1=ddname is allowed. The real question here is as per the links shared above and my understanding if ddname is SORTJNF1 then it’s not allowed but for any other name it’s has no issues and that’s why JCL SCAN gave the error. |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
The rel problem is that it is a JCL checker producing the messages not a utility control statement checker. I TS does not want the control statementrs checked then he should put hem nto a data set / member and reference that instead.
Topic locked as TS has not come back with any further information. |
|
Back to top |
|
|
|