TOO MANY CPU TIME by $DSCALL OPT=READ on SOLVE Operatiions

Article Id: 103242

Status: Published

Updated On: 31-08-2018 03:20

Products:

CA SOLVE:Operations Automation CA SOLVE: Access Session Management SOLVE:Access Session Management CA SOLVE:Access Session Management CA SOLVE:CA Mainframe Connector CA SOLVE:FTS

Issue/Introduction:

A NCL to read a file by $DSCALL OPT=READ.

When it reads the file having 10800 records, it takes CPU time 30s. Why does $DSCALL OPT=READ use so many CPU time ?

Environment:

Release:
Component: SOPJPN

Resolution:

Using $DSCALL DATA=* for the READ of the file is a lot more efficient, but does limit the reading of the file to the 1st 9,999 records, but this will save a lot of CPUTIME if the process can be adjusted to limit the input file size.