ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
TOO MANY CPU TIME by $DSCALL OPT=READ on SOLVE Operatiions
Article ID: 103242
Updated On:
Products
SOLVE:Operations Automation
SOLVE:Access Session Management
SOLVE:FTS
SOLVE
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 ?
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
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.
Feedback
Yes
No
Powered by
