SYNCSORT FOR Z/OS 1.1BR TPF1A U.S. PATENTS: 4210961, 5117495 (C) 2002 SYNC
xyz SYNSORT FOR Z/OS 1.1 z/OS
PRODUCT LICENSED FOR CPU SERIAL NUMBER 70AFC, MODEL 2064 105 LICEN
SYSIN :
SORT FIELDS=(15,3,BI,A,35,15,BI,A,18,4,BI,A,5,10,BI,A),NOEQUALS,
SIZE=E5000000,DYNALLOC=(PRDWRK)
WER164B 15,252K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,
WER164B 0 BYTES RESERVE REQUESTED, 920K BYTES USED
WER146B 104K BYTES OF EMERGENCY SPACE ALLOCATED
WER108I SORTIN : RECFM=VB ; LRECL= 19476; BLKSIZE= 23476
WER110I SORTOUT : RECFM=VB ; LRECL= 19476; BLKSIZE= 23476
WER453A FOR PARASORT SORTPAR2-4 UNITS CANNOT BE THE SAME AS THE SORTIN UNIT
WER211B SYNCSMF CALLED BY SYNCSORT; RC=0000
WER449I SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE
******************************* Bottom of Data ********************************
What is the code that precedes the error message?
Also, what level of SyncSort and the Operating System are you running? _________________ Alissa Margulies
SyncSort Mainframe Product Services
201-930-8260
zos_tech@syncsort.com
ICH70001I XXXXXX LAST ACCESS AT 10:49:57 ON THURSDAY, APRIL 5, 2007
IEF286I XXXXXXT1 SORTETRN SORTPAR2 - DISP FIELD INCOMPATIBLE WITH DSNAME
IEF272I XXXXXXT1 SORTETRN - STEP WAS NOT EXECUTED.
We are on z/OS and I am not sure about the level of sycnsort. This is what I see in the SYSOUT:
SYNCSORT FOR Z/OS 1.1CR TPF3A U.S. PATENTS: 4210961, 5117495
Also, as an fyi, for the file I had issues, i tried using the whole file name (including the generation) and it worked fine.
I run into issues only when I try to code the relative generation
TGDG.XXX.YYYY(0) - doesnot work
TGDG.XXX.YYYY.G0001V00 - No issues
But I want to do this PARASORT change to a job in production cycle and each week the generation changes. Well, I can code a Rexx or CLIST to allocate the complete name to SORTIN and call SORT dynamically. However, before doing so, I would like to take your suggestion, is there any direct solution that I can try?
It's a limitation in the way the system works. With Parasort we need to open the same dataset multiple times on different drives. With a relative reference to a GDG, this is not possible. Your REXX/CLIST approach would be an appropriate resolution. _________________ Alissa Margulies
SyncSort Mainframe Product Services
201-930-8260
zos_tech@syncsort.com
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum