Did you compare the two execution ? EXCP count ?
Syncsort decides to use or not use dataspace and in memory sort depending on the "LPAR status". So, compare the two sysouts and maybe you'll put light on the case. Especially look at the messages about I/O method used and the memory. Best regards. Massimo 2016-08-07 18:52 GMT+02:00 Nathan Astle <[email protected]>: > Hi > > We have upgraded our syncsort from 1.4.2 to 2.1 > > Post the upgrade there some batch jobs running too long which used complete > within 5min prior to upgrade. > > So to diagnose I have taken the dump of the batch job to pursue the issue > with syncsort. > > The Job was doing I/O but not sure why it was running too long without > completing. > > Did anyone face this issue at your shop ? > > Well Job log didn't show any errors using which I can research further. > > We are at zOS 2.1. > > SYSLOG or logrec too didn't give any much information > > Nathan > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
