MVSFORUMS.com Forum Index MVSFORUMS.com
A Community of and for MVS Professionals
 
 FAQFAQ   SearchSearch   Quick Manuals   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Processes that are high involving IO

 
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> Application Programming
View previous topic :: View next topic  
Author Message
SMS
Beginner


Joined: 16 Oct 2005
Posts: 53
Topics: 24

PostPosted: Sun Oct 16, 2005 11:28 pm    Post subject: Processes that are high involving IO Reply with quote

Hi,

Please let me know the exact cause of the following problem.

I tried to execute a job which has around 12 steps and most of it are
sort steps. At one step, a temporary dataset (15000 trks) passed from the previous step is getting passed to the subsequent step after getting
processed. At this point of the time, the job ran around 2 hours against
the usual 15 mins. Once I removed all the temporary datasets and
used cataloged datasets the problem is solved. But still other jobs
which uses temp datasets for huge volume runs without any problem.

Using a perofrmanc evalaution tool, when this process was evaluated,

it showed that there is reference to .COBLIB IGZCULE and IGZCXFR modules and there is a reference to Attribution of CPU execution time for I/O Logic Error Handler and I/O Declarative Transfer.

I could not understand what for these modules are (.COBLIB IGZCULE and IGZCXFR ) and the exact cause of this problem.
_________________
Regards,
SMS
Back to top
View user's profile Send private message
Phantom
Data Mgmt Moderator
Data Mgmt Moderator


Joined: 07 Jan 2003
Posts: 1056
Topics: 91
Location: The Blue Planet

PostPosted: Mon Oct 17, 2005 12:54 am    Post subject: Reply with quote

SMS,

Quote:

Once I removed all the temporary datasets and
used cataloged datasets the problem is solved.


Could be because of two reasons.
1. If the temporary datasets are huge, the job will definitely take some time to find out volumes that can accomodate the amount of space required. On the other hand, when you provide already cataloged datasets, it doesn't spend time hunting for space.

2. It also depends on the type of volume where your temporary datasets are stored. Note. the job takes significantantly longer time to allocate a dataset in a compressed volume compared to a normal volume. If you are forcing the jcl to allocate on compressed volume using DATACLAS parameter or if your shop default is to allocate all Temp. datasets on a compressed volumne then it might be the reason for the delay.

Find out where the temporary datasets are being stored.

Thanks,
Phantom
Back to top
View user's profile Send private message
kolusu
Site Admin
Site Admin


Joined: 26 Nov 2002
Posts: 12375
Topics: 75
Location: San Jose

PostPosted: Mon Oct 17, 2005 4:54 am    Post subject: Reply with quote

SMS,

IGZCULE and IGZCXFR are COBOL modules. Are you performing an Internal sort? i.e sort within a cobol program?

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu
Back to top
View user's profile Send private message Send e-mail Visit poster's website
SMS
Beginner


Joined: 16 Oct 2005
Posts: 53
Topics: 24

PostPosted: Mon Oct 17, 2005 10:42 pm    Post subject: Reply with quote

Hi Kolusu and Phantom,

DATACLAS PARAMETER :
1) Explicitly dataclas parameter is not used. But could you pls let me know how to check whether it is allocated on default ?.

EXTERNAL SORT :
2) I am performing external sort. Actually what happens is, step1 passes a
dataset to step2 after truncating the length to required size, step2 process this temp dataset by adding a keyfield in the existing filler clause after which is passed to another dataset. This is where issue starts.
_________________
Regards,
SMS
Back to top
View user's profile Send private message
kolusu
Site Admin
Site Admin


Joined: 26 Nov 2002
Posts: 12375
Topics: 75
Location: San Jose

PostPosted: Tue Oct 18, 2005 4:42 am    Post subject: Reply with quote

Quote:

2) I am performing external sort.


Sms,

I don't thinks so. If you are performing an external sort, how did the cobol modules come into picture. Post your JCL along with your sort sysin cards.

kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu
Back to top
View user's profile Send private message Send e-mail Visit poster's website
SMS
Beginner


Joined: 16 Oct 2005
Posts: 53
Topics: 24

PostPosted: Tue Oct 18, 2005 5:15 am    Post subject: Reply with quote

Kolusu,

Please find below the extract of that JCL. Actually problem occurs at step8

//STEP6 EXEC PGM=SORT,COND=(4,LT)
//SORTIN DD DSN=X.Y.Z,DISP=SHR
//SORTOUT DD DSN=&&CPXXXXXX,UNIT=SYSDA,
// DISP=(,PASS),
// SPACE=(CYL,(1500,300),RLSE),
// DCB=(RECFM=VB,LRECL=295,BLKSIZE=0)
//SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(550,350),RLSE)
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSIN DD *
SORT FIELDS=COPY
/*
//STEP7 EXEC PGM=SORT,COND=(4,LT)
//SORTIN DD DSN=&&CPXXXXXX,DISP=(OLD,PASS)
//SORTOUT1 DD DSN=&&CHXXXXXX,DISP=(,PASS),
// UNIT=SYSDA,SPACE=(CYL,(100,50),RLSE)
//SORTOUT2 DD DSN=&&CTXXXXXX,DISP=(,PASS),
// UNIT=SYSDA,SPACE=(CYL,(100,50),RLSE)
//SORTOUT3 DD DSN=&&CDYYYYYY,DISP=(,PASS),
// UNIT=SYSDA,SPACE=(CYL,(2500,500),RLSE)
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SORTWK DD
//SYSIN DD *
SORT FIELDS=(19,14,CH,A),EQUALS
OUTFIL FNAMES=SORTOUT1,INCLUDE=(5,2,BI,EQ,X'0080')
OUTFIL FNAMES=SORTOUT2,INCLUDE=(5,2,BI,EQ,X'0080')
OUTFIL FNAMES=SORTOUT3,INCLUDE=(11,4,CH,EQ,C'CHFI')
/*
//STEP8 EXEC PGM=APPEND,COND=(4,LT)
//STEPLIB DD DSN=TMS165.JQUERY.LOADLIB,DISP=SHR
//D500522I DD DSN=&&CDYYYYYY,DISP=(OLD,PASS)
//D500522O DD DSN=&&CAZZZZZZDISP=(,PASS),UNIT=SYSDA,
// SPACE=(CYL,(2500,500),RLSE)
_________________
Regards,
SMS
Back to top
View user's profile Send private message
kolusu
Site Admin
Site Admin


Joined: 26 Nov 2002
Posts: 12375
Topics: 75
Location: San Jose

PostPosted: Tue Oct 18, 2005 7:19 am    Post subject: Reply with quote

Quote:
Actually problem occurs at step8


Step 8 is execueting a COBOL pgm named Append. It is NOT an external Sort.

IGZCULE is a COBOL User I/O logic error handler and IGZCXFR6 is COBOL I/O declarative transfer.

It has nothing to do with Sort. Since both the modules have something to do with I/o , I would check the lrecl vs blksizes.

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu
Back to top
View user's profile Send private message Send e-mail Visit poster's website
SMS
Beginner


Joined: 16 Oct 2005
Posts: 53
Topics: 24

PostPosted: Tue Oct 18, 2005 11:19 pm    Post subject: Reply with quote

Kolusu,

The external sort I mentioned about is happening in Step7.
But the problem occurs only in Step8. In this step, both the
input and output will have the same file attributes.

Once temporary datasets are replaced with cataloged one, the job runs fine. That 's what I am wondering about since other jobs with temporary datasets of huge volume runs fine.
_________________
Regards,
SMS
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> Application Programming All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
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


MVSFORUMS
Powered by phpBB © 2001, 2005 phpBB Group