Originally posted by: SystemAdmin

Not being a mainframe person, I'm having a little trouble resolving a M/F performance issue. We are processing 78,000 fixed length 900-byte records (769 byte filler) using the Command Server in batch mode on MVS and exceeding the allotted execution time which is something like 50 minutes. The transformations are rather trivial: one record out for one record in with 3 LOOKUPs per record into a 300 line conversion table. Default workspace settings were used. On a Pentium III 696MHz 500MB desktop it only takes 8 minutes to run.

Can anyone recommend settings in or out of Mercator that might speed up processing?

Thanks, Jim Divoky, EC Solutions, Inc., 330-606-6826
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Hi
on MVS the issues are probably the following:
the job priority level, number of jobs running with higher priority
test region size(number of mips allocated to the test region) and total of jobs running at the same time, i would first up the priority level of the job i am running, are you running in work memory or work file in the map?
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Hi, Gary
>> are you running in work memory or work file in the map?

I'm using work files. Everything is at default values in the map at the moment.

Jim Divoky
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

running work memory will make it faster if the region is large enough but i would try upping the priority on the job first
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

I believe the region is 6MB. Everything I've read recommends using file based workspace for large files. I believe I was told or read a "large" file to Mercator is >300KB.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Check the RECFM, LRECL and BLKSIZE of your input file(s). RECFM=FB, with an LRECL=900 your BLKSIZE should be around 31500. Block the output files as large as possible, too. Specify REGION=0M. Workfiles, if you specify them, should have a BLKSIZE of 32760 if possible. Do be sure your JOBCLASS isn't labeled "discretionary work", or "low priority testing" or something similar.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender