Joined: 14 Jun 2006 Posts: 331 Location: Jacksonville, FL
I have been running an ICETOOL step with a PARM='EQUALS' on the execute statement. In the DFSMSG DD output, there are instances of EQUALS=N and EQUALS=Y. Why wouldn't every step run as EQUALS=Y if the PARM is coded as EQUALS? It makes a big difference when splicing two record together. I corrected the problem by adding an additional sort field that ensured the records are sorted correctly.
Joined: 14 Jun 2006 Posts: 331 Location: Jacksonville, FL
No tape files for sort work datasets.
I do have ICE143I messages:
Code:
ICE143I 0 BLOCKSET SORT TECHNIQUE SELECTED
No ICE800I.
The job was sorting correctly when we were under z/OS 1.10. When we went to z/OS 1.12 this past weekend, the particular sort in question did not keep records in "EQUALS" order even though PARM='EQUALS' is coded on the EXEC statement.
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
cpuhawg,
If you mean you are using PGM=ICETOOL,PARM='EQUALS', that will have no effect. PARM='EQUALS' is only used for PGM=ICEMAN, not PGM=ICETOOL. If you want to ensure that EQUALS is used for all ICETOOL operators, you would need to have:
Code:
//DFSPARM DD *
OPTION EQUALS
/*
in your ICETOOL step. That will override everything.
EQUALS is an installation and run-time option, so whether you end up with EQUALS or NOEQUALS in effect depends on where and how EQUALS is specified.
SPLICE set EQUALS, but it can be overridden elsewhere.
In order to tell you exactly what you're using in the way of EQUALS/NOEQUALS and where, I'd need to see a DEFAULTS run, and the complete JES listing for your ICETOOL run with SPLICE.
Joined: 14 Jun 2006 Posts: 331 Location: Jacksonville, FL
I tested your DFSPARM DD * and all EQUALS were set to 'Y' with the exception of one sort that was set to FIELDS=COPY.
We will use DFSPARM on all future jobs. It's odd the sort worked for over a year until we went under z/OS 1.12. My SYSPROG said the default is NOEQUALS.
The original problem was caused by only having 1 sort field and if all records were kept in order, everything worked fine. Had I coded a 2nd sort field, it would have ensured the SPLICE was occurring in the correct sequence.
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
EQUALS has no meaning for a COPY application. It is only used for a SORT or MERGE application.
Quote:
It's odd the sort worked for over a year until we went under z/OS 1.12. My SYSPROG said the default is NOEQUALS.
As I said, SPLICE sets EQUALS in effect, so if you were seeing NOEQUALS then something overrode the SPLICE setting. I'd need to see the complete JES log from the 1.10 and 1.12 runs to tell you what was different, but I'm sure something was.