Help required on SYSIN DD * maximum limits

kabyab

My requirement is to search for 10386 string values in a dataset. I need to know in which members in the dataset, each of those strings occur.

I have used ISRSUPC to code the following.
Here I have searched for two strings
SRCHFOR 'HBLI'
SRCHFOR 'LITE'

I need to know whether I can give 10386 entries under SYSIN DD * or is there any limit to it?

Also if I am providing the 10386 entires through some control card, then how many control cards at max can be coded in a JCL?

expat · Posted: Thu May 08, 2008 4:04 pm Post subject:

What have you found in your own research that prompts to ask the question ?

dbzTHEdinosauer · Posted: Thu May 08, 2008 4:24 pm Post subject:

if you use the parm IDPFX, you will make your output much easier to scrape (use).

i ran a test with 100,000 control cards and reached a memory limit. probably could have increase my region size and it would have worked, but what would i do with the output from a search of 100,000 items?

works with 14,000 without region size change.

again, how are you going to process this output file - by hand?

kabyab · Posted: Thu May 08, 2008 5:22 pm Post subject:

The requirement is such that we need to move a considerable number of members from a LOAD LIBRARY dataset to another new dataset. That Load Library is being referred to in many of our JCLs in the STEPLIB. We need to find out the how many of our JCLs are impacted i.e. dependent on those members which are being moved.

I was planning to put the member names in the SRCHFOR list and against NEWDD I will be using the JCL dataset.

Then we can find out how many members from the LOAD library are being referred to in the JCL.

I saw an earlier post where it was written that we can put as many entries as we like in the SRCHFOR list. So I was kind of wondering whether there is a limit to the number of entries we can mention in there.

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1480

Hi Kabyab,

Why don't you just try it? I assume you've got a list that can be cut pasted into a file or PDS member. Just propagate the SRCHFOR with M/OO and use the file/member as SYSIN.

If SUPRC coughs it up, find the max it will take and you can break SYSIN into segments and do multiple runs. Then combine & edit the O/Ps.

Anuj D. · Posted: Thu May 08, 2008 11:34 pm Post subject:

Hi,

Try using