> I have to ask. What's harm of defining a couple 1 cylinder (or 2 track) OCDS,
> BCDS that will remain empty and unused?
'Business reasons'.
I just didn't understand why something that looks to have correct syntax is
getting a syntax error. Turns out that it *should* be correct. I will just
sh
2013 9:14 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Installing HSM or rather: DFHSM woes
>
> Glenn,
>
> > Have you tried an HSM Modify command to issue it? The syntax seems
> correct, so it may be some typographical error in your parmlib.
>
> 1319
Glenn,
> Have you tried an HSM Modify command to issue it? The syntax seems correct,
> so it may be some typographical error in your parmlib.
13193 06:03:58.69 me 0290 F DFHSM,SETSYS TAPEMIGRATION(NONE)
13193 06:03:58.71 STC02475 0090 ARC0103I INVALID SETSYS PARAME
Hi, I discovered that we modified the syntax in the Storage Admin between v1R12
and V1R13. V1R13 (which I looked at) incorrectly shows the left paren to the
immediate right. I looked at the code and saw that the subparameter is not
required, so I'll get the syntax corrected back to the way it
> SETSYS TAPEMIGRATION(NONE is looking for the next set of subparms. In the
> syntax diagram, note the left paren after NONE, which means it wants another
> parameter - ROUTETOTAPE(ANY | unit).
|_NONE__ ___ _|
|_(__ _ROUTETOTAPE_ __
Hi
On 08.07.2013 19:41, Glenn Wilcock wrote:
Hi,
Just got back from vacation and saw this thread. SETSYS TAPEMIGRATION(NONE is
looking for the next set of subparms. In the syntax diagram, note the left
paren after NONE, which means it wants another parameter - ROUTETOTAPE(ANY |
unit).
Hi,
Just got back from vacation and saw this thread. SETSYS TAPEMIGRATION(NONE is
looking for the next set of subparms. In the syntax diagram, note the left
paren after NONE, which means it wants another parameter - ROUTETOTAPE(ANY |
unit).
I don't believe that you have the correct understan
I believe the one of the earlier suggestions to define the CDS's, even if
treated as "dummy" will greatly reduce your woefulness .
" Can anybody tell me why SETSYS TAPEMIGRATION(NONE) gets ARC0103I INVALID
SETSYS PARAMETER TAPEMIGRATION ?"
Seems to be either a "sequencing" error (e.g. migration
, July 04, 2013 5:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Installing HSM or rather: DFHSM woes
> Is this in the ARCCMDxx member? Or is it being issued as a command?
Doesn't matter. Doesn't work either way, gets the same error message.
> If in the ARCCMDxx can you post a few
> Is this in the ARCCMDxx member? Or is it being issued as a command?
Doesn't matter. Doesn't work either way, gets the same error message.
> If in the ARCCMDxx can you post a few lines above and below the
> Tapemigration line?
SETSYS -
O
, an Offline control dataset is required.
Lizette
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of nitz-...@gmx.net
Sent: Wednesday, July 03, 2013 11:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Installing HSM or rather: DFHSM woes
Alan,
> You can issue F DFHSM,RELEASE MIGRATION, but it will most likely be held
> again immediately when the first migration is attempted.
I got up the nerve to issue the command this morning (after all, the cycle is
still defined to not start by itself).
HSM said: ARC0100I RELEASE COMMAND
323-715-0595 Mobile
jo.skip.robin...@sce.com
From: "nitz-...@gmx.net"
To: IBM-MAIN@LISTSERV.UA.EDU,
Date: 07/03/2013 08:16 AM
Subject: Re: Installing HSM or rather: DFHSM woes
Sent by:IBM Mainframe Discussion List
> DUMMY muddies the water because
>
> DUMMY muddies the water because
> the DDNAME is truly allocated even though there is no tin can at the other
> end of the string. A component that wants to use that file may well try to
> open it. Depending on how the file is accessed, DUMMY can cause OPEN
> failure.
Well, not in the case of
;Staller, Allan"
To: IBM-MAIN@LISTSERV.UA.EDU,
Date: 07/03/2013 06:45 AM
Subject:Re: Installing HSM or rather: DFHSM woes
Sent by:IBM Mainframe Discussion List
The journal is used to rebuild the xCDS dataset in the event of the xCDS
being damaged, I would strongl
The journal is used to rebuild the xCDS dataset in the event of the xCDS being
damaged, I would strongly suggest that you plan for a journal.
You will need to manually schedule "F DFHSM,BACKVOL CDS" to periodically clear
the journal since you are not performing functions that would result in the
Finally I have finished wading through the HSM starter set and customized it
the way we want to use it - just migrating to ML1, no ML2, no backup, no
recovery, no dumping, no tapes, a really minimal environment. That means I only
start DFHSM with an MCDS (OFFCAT, BAKCAT, JOURNAL, ARCLOGX, ARCLOG
17 matches
Mail list logo
