Mainframe, MVS and zOS Discussion

BMC Mainview or Omegamon both let you look at storage usage while the program is running.  Either of them would be the place to start.

Understanding your data is absolutely critical. Your requirements would be completely different for a data set with record lengths varying from 100 to 200 bytes as opposed to one with a base record length of 900 bytes and a maximum record length of 32767 bytes. You also want to understand how ...

It definitely looks like you don't know what you're talking about -- your post title mentions 337M records while your post says 297M rows and then there is "data volume 163M records". I'm assuming you mean millions for each M although you did not specify. Questions you need to research include ...

File status 92 on a VSAM file is frequently caused by not establishing a current record pointer before doing a read.  If your VSAM is dynamic, move LOW-VALUES to the key and do a START before the READ.  Otherwise, you'll need to post the FILE definition and the READ code for us to review.

It doesn't really matter what you think -- the computer is telling you that there is bad data somewhere causing the S0C7.  Until you start trusting the computer and closely scrutinizing your data, you will fail to identify the issue.

A tape management system is, by far, the easiest way to get what you want. Ask someone at your site (system programmer, operator, or other systems person) to find out if your site uses a tape management system.

If your site doesn't use a tape management system, your next best bet would be to write ...

You could probably use DCOLLECT but it could take a while to set it up correctly.

Are you really sure you want this?  There may thousands or tens of thousands of VSAM data sets on any given mainframe.  Your output may run several million lines.

There is no easy way to do this since there are no standard ways to name data sets.

If you are talking about the difference between EXEC CICS CALL and EXEC CICS XCTL, the former acts as a subroutine call and will return to the program (the statement after the EXEC CICS CALL) when the subprogram ends whereas the latter transfers control to the new program and does not return to the ...

I mean what if there was no AMODE or it was very less like 8-bit, what exactly would happen? Why is the concept needed?


Prior to IBM's announcement of 31-bit addressing in 1983, there was no such thing as AMODE or RMODE. An address was 24 bits -- period. One thing to keep in mind is that IBM ...

AMODE is addressing mode, or how many bytes of memory can be addressed
RMODE is residency mode, or where the load module is loaded into memory

The original S/360 in 1964 used 24 bits (out of the 32 bits in the word) for addressing. This allows 16,777,216 bytes of memory to be addressed. AMODE 24 ...

Find and study RFC 5321, which is the Internet standard way to use SMTP to send mail. Sending attachments usually requires experimentation as the format is EXTREMELY picky and one wrong character may cause the attachment to not send. Also, your site must have enabled the SMTP writer. I recommend ...

If the input file is sequential, you cannot directly read the last record.

Your question makes as much sense as asking "how high is up?" "Better" can be defined in different ways (such as lowest memory used, fastest execution time, easiest to modify, etc.) and hence the answer to your question will depend upon what you're wanting to optimize.

In general, dynamic calls ...

You could get 9 of these blocks onto one track (56664 divided by 6160)

This is not accurate as there is system overhead as well.  Manual GX26-4577 has the details for 3390 devices and it shows only 8 blocks of size 6160 will fit on a track.

Edit the JCL to delete the other steps and submit it.

Read the RERUN clause in the I-O-CONTROL paragraph starting on page 154 of the version 6.4 of Enterprise COBOL Language Reference manual.  You will probably also want to review the RERUN information in the Programming Guide manual.

You can only pass ONE parameter from JCL to COBOL.  You can parse that parameter any way you need, but it is only one parameter with one entry in the LINKAGE SECTION.

Why on earth would you want to do this?  IDCAMS is easy to use and efficient.  You could write a program to do the copy, but you'd have to write a program for every single copy you want to do -- use IDCAMS.

You will need to learn how to read the dump -- that will tell you the exact record with the problem and point you towards where the S0C7 occurred.