|
View previous topic :: View next topic
|
| Author |
Message |
Singaram
New User
Joined: 19 Aug 2009
Posts: 19
Location: India
|
|
|
|
Its known that usage of a COBOL sort verb invokes DFSORT internally. At the same time even if FASTSRT compiler options is used the I/O is being taken care by the E15 and E35 exit routines of DFSORT if INPUT & OUTPUT PROCEDURE is used along with the SORT verb in COBOL.
1. Now how can I identify from the DFSORT messages that I/O was performed by COBOL exit routines or DFSORT itself??
2. Can we find out the DFSORT SORT CARD internally used which is associated with the corresponding COBOL SORT verb?
Thanks in advance.. |
|
| Back to top |
|
 |
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005
Posts: 7129
Location: San Jose, CA
|
|
|
|
Add this to your COBOL JCL:
| Code: |
//DFSPARM DD *
OPTION MSGPRT=ALL,LIST,MSGDDN=MYMSGS
/*
//MYMSGS DD SYSOUT=*
|
1. If COBOL performs the input, you will see message ICE089I in MYMSGS. If DFSORT performs the input, you will see message ICE088I in MYMSGS.
If COBOL performs the output, you will see message ICE091I in MYMSGS. If DFSORT performs the output, you will see message ICE090I in MYMSGS.
2. The DFSORT SORT statement will be listed in MYMSGS. |
|
| Back to top |
|
|
Singaram
New User
Joined: 19 Aug 2009
Posts: 19
Location: India
|
|
|
|
Thanks a lot Frank...
Will definitely add this to the JCL and let you know for any updates.
Isnt there any performance degradation because of printing all the messages?? |
|
| Back to top |
|
|
Frank Yaeger
DFSORT Developer
Joined: 15 Feb 2005
Posts: 7129
Location: San Jose, CA
|
|
|
|
| Quote: |
| Isnt there any performance degradation because of printing all the messages?? |
Seems like an odd question given you asked "how to identify from the DFSORT messages" which assumes you want to print the DFSORT messages.
The real question should be: Is there a significant performance degradation from printing the messages.
If you are sorting a small number of records, then the CPU time would be small and the additional CPU time for printing the messages might be noticable, but shouldn't be significant given the small CPU time.
If you are sorting a large number of records, the added CPU time for printing the messages shouldn't be significant compared to the total CPU time. |
|
| Back to top |
|
|
Singaram
New User
Joined: 19 Aug 2009
Posts: 19
Location: India
|
|
|
|
Im extremely sorry for an indirect way of asking the question..
Because I just got a doubt whether I can use it in all places in production to extract the messages or to use only in case of long running codes...
Once again Im sorry for an odd question will make sure not to repeat next time...
Thanks for the details |
|
| Back to top |
|
|
|
|
