View previous topic :: View next topic
|
Author |
Message |
seman18
New User
Joined: 08 Feb 2009 Posts: 67 Location: hz
|
|
|
|
enrico-sorichetti wrote: |
Code: |
**ERROR - DSS4940E - UNABLE TO IDENTIFY UNIT NAME "PARE44 " |
the esoteric names You are using are not defined
what was not clear in the syncsort manual quote ??? ...
Quote: |
For optimal PARASORT performance, SyncSort must be able to read each SORTPARn input DD simultaneously, with no channel contention. To ensure this, your system programming staff may have defined special esoteric unit names for use with PARASORT. Before creating a PARASORT application, you should contact your system programmer to verify that this work has been done and that the special names are available for use.
Note, however, that even if the work has been done, certain categories may be unavailable due to limited channel capacity.
To use special esoteric names, do the following:
1. Decide whether you would like to specify 4-way (up to SORTPAR4), 3-way (up to SORTPAR3) or 2-way (up to SORTPAR2) input.
2. In the table of special esoteric names provided by your systems programmer, find the name that corresponds to the tape type of the SORTIN data sets.
The following is a sample table of special esoteric names. This table is for illustration only; the names at your site may be different. |
|
below is what I got through "SYNCLIST"
Code: |
3420 3480/90 3490E 3590
|----------|----------|----------|----------|
4-WAY | NOT | NOT | PARE41 | NOT |
INPUT | POSSIBLE | POSSIBLE | PARE42 | POSSIBLE |
| | | PARE43 | |
| | | PARE44 | |
|----------|----------|----------|----------|
3-WAY | NOT | NOT | PARE31 | NOT |
INPUT | POSSIBLE | POSSIBLE | PARE32 | POSSIBLE |
| | | PARE33 | |
|----------|----------|----------|----------|
2-WAY | NOT | NOT | PARE21 | NOT |
INPUT | POSSIBLE | POSSIBLE | PARE22 | POSSIBLE |
|----------|----------|----------|----------|
|
|
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
OOPS.. the message prefix DSS.....
seems that You are running some kind of jcl checker
( DSS is not an IBM message prefix )
if the esoterics have been properly setup then the jcl checker is giving false warnings
Quote: |
The Parasort Esoteric Unit Name Table produced by the SYNCLIST report program should provide the available drives. |
... I am not the only one to have overlooked Your sentence...
Quote: |
got the SYNCSORT Programming guide, and use the synclist to get the following information |
|
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
As I said earlier - Tuning SyncSort is usually application specific and to get you better replies we'll be intrested to see "B" messages, which you have not shown yet. Having said that, your best bet is to get in contact with Alissa (Margulies) with those details on her e-mail ID. |
|
Back to top |
|
|
Alissa Margulies
SYNCSORT Support
Joined: 25 Jul 2007 Posts: 496 Location: USA
|
|
|
|
Please note, PARASORT cannot be used with a SORTIN GDG with a relative reference specified. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
That's a nice tip Alissa to remember, but what's the work around then? |
|
Back to top |
|
|
Alissa Margulies
SYNCSORT Support
Joined: 25 Jul 2007 Posts: 496 Location: USA
|
|
|
|
One option is to code an absolute GDG for SORTIN... another option is to code a standard sort - don't use PARASORT. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Thanks Alissa, that helps.
Have a good one |
|
Back to top |
|
|
|