I don't think this is an SMS problem, SMS would not allocate a (new) dataset to
a non-existing volume.
I think the dataset exists and is cataloged to a volume that is not available
in your system. What does the catalog say about this dataset?
Sometimes it is more efficient to ask help for your o
You might be able to save the 'corrupted' PDSE like this. It's worked for me
the last few times.
D SMS,PDSE1,CONNECTIONS,DSN(pdse-name)
D SMS,PDSE,CONNECTIONS,DSN(pdse-name)
(to see which address space is managing this PDSE - call this sms-address-space)
V SMS,,REFRESH,DSN(pdse-name)
Regards an
On Mon, 27 Feb 2017 22:20:07 -0400, Clark Morris wrote:
>When did it change to 100?
Some time between 1967 and 1970.
See page 85 of
http://bitsavers.trailing-edge.com/pdf/ibm/360/os/R19_Jun70/GC28-6704-0_JCL_Reference_Rel_19_Jun70.pdf
for OS/360, dated June, 1970
PARM=value
value
consists of
Tom Marchant wrote:
>Some time between 1967 and 1970.
I think the limits of 40 or 100 characters were based on a quick way (without
using tapes or extra punch cards) to give shortish parameters to a program
using puch cards. Or so it was told to me by an oldie years ago.
About "Reference of t
Oh man, that brings back some memories. Check out Figure 3 on page 25 of the
1970 manual!
Interesting -- the example of a possible PARM= value ('P1,123,MT5') has not
changed between that manual and
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieab600/iea3b6_Syntax89
On Tue, 28 Feb 2017 07:25:32 -0600, Elardus Engelbrecht wrote:
>Tom Marchant wrote:
>
>>Some time between 1967 and 1970.
>
>I think the limits of 40 or 100 characters were based on a quick way (without
>using tapes or extra punch cards) to give shortish parameters to a program
>using puch cards.
On Mon, 27 Feb 2017 14:54:49 -0500, John Eells wrote:
>Paul Gilmartin wrote:
>
>>>
>> You're suggesting that a transcript or summary of those discussions
>> is available. Can you cite? Thanks.
>>
>
>
>I suggested neither one, so I am a bit puzzled about how you inferred
>that. What I wrote was,
We saw a 2X increase in JES2 CPU usage before the PTF was applied. Afterwards
the JES2 CPU usage was consistent with what we saw at z/OS 2.1.
On Mon, 2/27/17, SrinivasG wrote:
Subject: Re: z/OS 2.2 Question
To: IBM-MAIN@LISTSERV.UA.EDU
Date: Mon
On Tue, 28 Feb 2017 10:19:49 -0600, Paul Gilmartin wrote:
>Ah! That shows that (at least at one time) it was possible to increase
>the length of the PARM without introducing intolerable incompatibilities.
Perhaps because the potential integrity issues were not understood at the time.
>Where's
There were no APF authorized programs ...
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Tom Marchant
Sent: Tuesday, February 28, 2017 9:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL History (was: ... PARMDD ... )
On
On Tue, 28 Feb 2017 11:21:50 -0600, Tom Marchant wrote:
>
>>I'm curious because others have said (in this forum?) that earliest PROCs
>>had no arguments; all modification was done by overrides. So, at that
>>time symbols didn't exist in JCL, neither as PROC formal parameters nor
>>in the (relative
On Tue, 28 Feb 2017 09:41:43 -0800, Charles Mills wrote:
>There were no APF authorized programs ...
>
But there was the hazard of buffer overruns even in unauthorized programs.
IBM provides features to protect its code without timely extension of such
features to customer-written code. Consider
Hello all, we set up a sandbox LPAR where we just basically copied all the
operating environment (z/OS 2.2) from prod system to the sandbox. What we want
to do is turn off or nullify the SMS routines for a short time. I have spent
all morning and part of the afternoon looking for a way to do tha
On Tue, 28 Feb 2017 20:46:16 +, Ward, Mike S wrote:
>What we want to do is turn off or nullify the SMS routines for a short time.
Do you mean that you want all new data sets to be non-sms managed?
If so, you will need to have some volumes that are not SMS-managed.
You could change the STORC
the DFSMS storage Admin guide helps 'setting up' SMS because that's basically
what your doing, at the very least I think you'll need a storage class routine
with a small Filterlist (maybe) and a SELECT WHEN that passes a NULL storage
class
SELECT
WHEN (&some criteria is met) < - this never
Thanks for the reply
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Tom Marchant
Sent: Tuesday, February 28, 2017 2:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMS Routines help
On Tue, 28 Feb 2017 20:46:16 +, Ward, Mike S wr
Thank you for the reply.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Carmen Vitullo
Sent: Tuesday, February 28, 2017 2:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMS Routines help
the DFSMS storage Admin guide helps 'setting
Ward,
Why do you want to nullify the SMS functions? Just curious?
I think you can have very simple ACS Constructs, like others have posted. Or I
think you can have an empty SCDS (not sure you would need to look this up)
When you copied the datasets and catalogs from PRD to Sandbox, you probably
_Massive Amazon cloud service outage disrupts sites_
(http://www.usatoday.com/story/tech/news/2017/02/28/amazons-cloud-service-goes-down-sites-scramble
/98530914/)
Wondered why traffic was a little off.
--
For IBM-MAIN subsc
Because doing a TSO/PDF submit we keep getting these errors, and we believe it
is an SMS probem.
,IKJ56221I DATA SET S250MWE.SPFTEMP0.CNTL NOT ALLOCATED, VOLUME NOT AVAILABLE+,
,IKJ56221I VOLUME NECESSARY TO SATISFY YOUR REQUEST NOT ON SYSTEM, AND CANNOT B
E MOUNTED,
,***,
-Original Message
Hi Ed!
I'm doing an AWS class and was online fiddling with my EC2 instance when it
happened. I use us-west-1a (I'm in Colorado), but there was some increased
response even there - maybe as they moved resources?
I thought this was not supposed to happen, ever. Should be interesting to
That indicates you need to modify your storage group(s) to use the volumes
available to the system. Your storage groups still have the other systems
volumes defined. So your system is attempting to define stuff on those
volumes, which don't exist on your sandbox system.
Matthew
On Tue, 28 Fe
The notice says check the Dashboard for updates. They seem to have one or
two of these a year. So far they've been pretty tight lipped about it.
In a message dated 2/28/2017 5:35:37 P.M. Central Standard Time,
bles...@ofiglobal.com writes:
I'm doing an AWS class and was online fiddling wi
Might need to adjust VATLST. There are several ways to look. PDS vol * stor
| pub | priv will tell you what's mapped to which group.
In a message dated 2/28/2017 5:52:11 P.M. Central Standard Time,
mathwst...@bellsouth.net writes:
on those volumes, which don't exist on your sandbox syst
Yep, I've had the dashboard up since this morning.
I'll be interested to learn what (if any) recourse paying customers have if
they can say (and prove): " I lost $ due to this outage"
VMs that don't (automatically?) have access to the replicated data within the
AZ? That would be bad.
Mo
On Tue, 28 Feb 2017 17:46:46 -0500, Edward Finnell wrote:
>_Massive Amazon cloud service outage disrupts sites_
>(http://www.usatoday.com/story/tech/news/2017/02/28/amazons-cloud-service-goes-down-sites-scramble
>/98530914/)
>
>Wondered why traffic was a little off.
>
That URL is broken by wrap.
I was going to add, see what Storage Group your ISPF datasets are allocated to,
then adjust that Storage Group with SMS Volumes in your sand box.
As was pointed out, you will probably need to update all of your Storage
Pools/Groups to reflect the DASD on the sandbox. Unless you keep the volser
_Amazon's cloud VP was on stage talking up AWS at the very moment it went
crashing down - AOL Finance_
(https://www.aol.com/article/finance/2017/02/28/amazons-cloud-vp-was-on-stage-talking-up-aws-at-the-very-moment/21864170/)
Oh darn.
-
Has anyone else experienced this?
A vendor for a mainframe data entry product used for the last 30 years (with a
perpetual unlimited seat license) has sent us a contract addendum where they
increase the price by 60+% and include language to change to a MSU based
license.
The use of this produc
John Thinnes wrote:
>A vendor for a mainframe data entry product used for the
>last 30 years (with a perpetual unlimited seat license)
>has sent us a contract addendum where they increase the
>price by 60+% and include language to change to a MSU
>based license. The use of this product is dwindling
Timothy Sipples wrote:
If a vendor wants to charge $2
per user hair follicle per fortnight
If that's head hair (as opposed to beard hair) I'd be in great demand, we'd get
the software for next to nothing.
--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.
We maintain over 100 sites either fully or partially, and we run into this type
of problem from time to time.
We had a recent problem where our Software AG software attempted to increase
the cost based on SAG MSU's instead of IBM MSU's, even though the box had not
changed (just the location was
32 matches
Mail list logo
