Can anyone tell me where to find the meaning of 0C return code ?? I tried
the MVS msgs and it's not there.
Have you tried IBM's LookAt? Lets you lookup messages online.
http://www-03.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/
Now, as to what it means.
When you do backups with Concurrent Copy (the CONCURRENT operand of
DFSMSdss DUMP or COPY command), the System Data Mover (SDM, a z/OS
component) establishes a Concurrent Copy session in the control unit
covering the tracks for the datasets or volume being backed up. If any
tracks are updated in those datasets or volumes, the pre-update copy of
the tracks are placed in a cache 'sidefile'. The SDM is responsible for
saving those pre-updated track images in a z/OS data space to empty the
side file. The side file is usually not very large; once it exceeds 3
tracks the control unit starts urging SDM to empty it. I think the max
is 128 tracks in the sidefile per CC session.
So the message indicates that you are using Concurrent Copy, and that
some CC session is approaching the max for its sidefile, which means
that SDM is not emptying it fast enough. This could mean a SDM failure
or bug, or it could just mean that some application is updating the data
so fast that the SDM can't keep up. I think that the control unit
will just delay the application update I/O with a "long busy" on the
disk until the SDM can catch up.
If the problem is causing application or backup failures, you need to
contact IBM. If not, this is probably not a problem unless the
messages keep recurring for a long time.
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
