it was superseded by UJ02346 in PUT2003 which was contained in RSU2006. so I
would imagine that if it was already supped just 2 months later that getting it
now would probably not be a productive use of your time.
While you can install by PUT, I would not. I think it's far better to stick
Thanks for the replies.
I ordered UJ01255, it had PUT2001 (no RSU 8 months later).
I did raise the issue with support, was told :
UJ01255 was not included in RSU2001.
It didn't not meet the following criteria:
-Severity 1 or 2
-HIPER
-PEFIX
CNOP 0,8?
On 30/09/2020 14:13, Peter Relson wrote:
>> ORG *,8
> Curious: Does this do anything that "DS0D" doesn't do?
> Wouldn't "DS0D" be more typical for "I want the next thing to be on a
> doubleword boundary?
> It certainly is for those of us who learned assembler long before
Since I'm seeing nothing applied and no errors listed, my best guess is that
any PTFs in the GLOBAL zone are;
1) Already applied
2) For different FMIDs from those that are already installed in the target zone
3) For a different SREL
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted
I have a sourceid in a global zone that doesnt show up in the target zone. When
I run an apply it fails with :
APPLY
PTFS
APARS
I don't believe so. Which other platforms?
https://man7.org/linux/man-pages/man3/usleep.3.html
On Wed, Sep 30, 2020 at 4:19 PM Phil Smith III wrote:
> The usleep() function in z/OS is documented as taking a single operand
> that must be less than 1M; on other platforms, it must be *at least*
The usleep() function in z/OS is documented as taking a single operand that
must be less than 1M; on other platforms, it must be *at least* 1M. It also
generates no error, and just returns instantly if you give it a value of 1M or
more.
This seems.poor. Anyone got any insight/guesses? Yes,
On Tue, 29 Sep 2020, at 23:57, Paul Gilmartin wrote:
> Similarly, I once created a data set such as:
> DD DISP=(NEW,CATLG),DSN=hlq.X.FOO-BAR
> No problem. Later, I tried
> DD DISP=(NEW,CATLG),DSN=hlq.Y.FOO-BAR,
>DCB=hlq.X.FOO-BAR
> Again, the hyphen caused a syntax error. The
Also known as the “chicken out” prompt. :-)
On Wed, Sep 30, 2020 at 14:50 Pommier, Rex wrote:
> z/OS 2.4, it does not remember shutting those options off. I'm OK with
> the behavior and could take it either way but I know I'd be recovering user
> datasets much more often if the "are you
When you define the certificates to RACF do you have to issue some kind of
RACF refresh command for ICSF? In my case we use Top Secret.
I have followed your list of debug tips and I can't find anything wrong.
Except for the question I posed.
Thank you,
Roberto
On Wed, Sep 30, 2020 at 9:17 AM
z/OS 2.4, it does not remember shutting those options off. I'm OK with the
behavior and could take it either way but I know I'd be recovering user
datasets much more often if the "are you sure" wasn't there.
Rex
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
I *think* it remembers the option on the main panel, assuming you actually exit
ISPF rather than 622'ing.
I *like* the behavior. I don't mind the extra "are you sure?" on a single
dataset delete -- has saved my @ss once or twice -- and if I am deleting a
bunch, I set it off on the first
Peter,
We are running NVAS 2.1, but it has been a LONG time since we implemented it
and I don't remember all of the details.
Here is link to the manuals if you don't have it already:
http://publib.boulder.ibm.com/tividd/td/NetViewAccessServices2.1.html
IIRC there are 2 exits provided by IBM.
On Wed, 30 Sep 2020 10:51:36 -0700, Charles Mills wrote:
>
>For dataset delete from 3.4?
>
>On the main panel
>
>Enter "/" to select option
>/ Confirm Data Set Delete
>/ Confirm Member Delete
>
>And on the delete panel
>
>Enter "/" to select option
> Set data
> And I was irritated when ISPF, which I had long been using suddenly began
> requiring confirmation on "Delete"; no profile to disable it.
For dataset delete from 3.4?
On the main panel
Enter "/" to select option
/ Confirm Data Set Delete
/ Confirm Member Delete
And on
Well, when I dump a catalog I don't want to dump the associated data sets, but
catalogs are very different animals from Uix directories.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Paul
ORG *,8 doesn't do anything that DS 0D doesn't do, but ORG *,256 has no DS
equivalent.
The syntax diagram in the HLASM reference shows ORG ,8 to be invalid syntax, so
there is no way that the message could be legitimate; there should have been a
message for syntax error.
Of course, it would
An APAR would be appropriate for the incorrect error message, and you might
consider an RFE to allow alignment on an omitted (high bound) relocatable
expression.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion
Rule 0: If your data-entry form has syntax requirements, indicate them on the
form. That includes requiring or prohibiting punctuation.
As for uppercasing the local part of an e-mail address, that is the sin for
which there is no forgiveness.
--
Shmuel (Seymour J.) Metz
On Wed, 30 Sep 2020 15:44:14 +, Seymour J Metz wrote:
>Applications should diagnose but not "correct" user errors, and should use
>comoon system services to do so, where they exist. OS developers should
>provide services for validation. Neither application developers nor OS
>developers
Applications should diagnose but not "correct" user errors, and should use
comoon system services to do so, where they exist. OS developers should provide
services for validation. Neither application developers nor OS developers
should attempt to validate externally defined data unless they
HLASM is a mainframe assembler, so it's legitimate here. It's also legitimate
on the assembler list, with a smaller but more focused audience.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Yeah, like every rule, there are exceptions. If on some particular system there
were a very high overhead for a failed file open (or some analogous operation)
then that might justify pre-validating an operand.
Charles
-Original Message-
From: IBM Mainframe Discussion List
On Wed, 30 Sep 2020 13:59:02 +, Pommier, Rex wrote:
>
>OK, thanks. I hadn't considered the "I'm going to because I can" angle,
>namely because I'm more of the "why would you even want to do that, even if
>you can, it'll cause problems." Kind of guy. But I know the adage, every time
You are correct. For now, you must specify all the path names, but we
understand this is a capability that ought to be provided in DFSMSdss. As
others have mentioned, you may be able to use other tools to craft a list of
path names and use that to generate DFSMSdss SYSIN statements. There is
Thank you both Wendell and Mike.
I am following your recommendations
for debugging.
On Wed, Sep 30, 2020 at 9:17 AM Wendell Lovewell <
01e9c0ee0673-dmarc-requ...@listserv.ua.edu> wrote:
> Hello Roberto.
>
> In RACF-land, I'd look for an ICH message on the console to make sure you
> don't
Gil,
OK, thanks. I hadn't considered the "I'm going to because I can" angle, namely
because I'm more of the "why would you even want to do that, even if you can,
it'll cause problems." Kind of guy. But I know the adage, every time somebody
makes something foolproof, the universe comes up
On Wed, 30 Sep 2020 09:13:57 -0400, Peter Relson wrote:
>>ORG *,8
>
>Curious: Does this do anything that "DS0D" doesn't do?
>
What construct allows the user to control the content of the slack bytes?
How much does it matter?
What construct truncates the TXT record?
How much does it
On Wed, 30 Sep 2020 08:01:09 -0500, Walt Farrell wrote:
>On Tue, 29 Sep 2020 16:59:34 -0700, Charles Mills wrote:
>
>>Applications should not "validate" filenames before attempting to open or
>>create a file. Present the name to the file system API and report any error
>>back to the user.
On Sep 30, 2020, at 8:13 AM, Peter Relson wrote:
>
>> ORG *,8
>
> Curious: Does this do anything that "DS0D" doesn't do?
> Wouldn't "DS0D" be more typical for "I want the next thing to be on a
> doubleword boundary?
> It certainly is for those of us who learned assembler long before
Hello Roberto.
In RACF-land, I'd look for an ICH message on the console to make sure you don't
need to PERMIT the client or the server access to the keyring. I've found the
gsk trace file to be very helpful--if the security manager doesn't tell you via
a console message. Telling PAGENT
>ORG *,8
Curious: Does this do anything that "DS0D" doesn't do?
Wouldn't "DS0D" be more typical for "I want the next thing to be on a
doubleword boundary?
It certainly is for those of us who learned assembler long before SECTALGN
(and this form of ORG) even existed.
It might be true
On Tue, 29 Sep 2020 16:59:34 -0700, Charles Mills wrote:
>Applications should not "validate" filenames before attempting to open or
>create a file. Present the name to the file system API and report any error
>back to the user. Application filename validation is what leads to these
On Tue, 29 Sep 2020 19:58:06 -0500, Paul Gilmartin wrote:
>On Tue, 29 Sep 2020 16:59:34 -0700, Charles Mills wrote:
>
>>Applications should not "validate" filenames before attempting to open or
>>create a file. Present the name to the file system API and report any error
>>back to the user.
>Is it possible to delete a E-MLPA module dynamically ?
No. Why would you want to?
It is possible to delete a dynamic-LPA module dynamically but it is almost
always a system integrity error to do so because it is often impossible to
be certain that there is no code executing within it
On Wed, 30 Sep 2020 20:35:11 +1000, Andrew Rowley wrote:
>On 30/09/2020 6:03 pm, Seymour J Metz wrote:
>> The DSS manual say that when you specify a directory, it does not dump the
>> files under that directory. That's very different from the behavior of,
>> e.g., tar.
>
>I guess I shouldn't be
I'm hoping that it's still a 'work in progress' & that one day I'll be able
to say 'DUMP PATH INCLUDE('/foldera/folderb/**') or something close to that.
Sean
On Wed, 30 Sep 2020 at 11:35, Andrew Rowley
wrote:
> On 30/09/2020 6:03 pm, Seymour J Metz wrote:
> > The DSS manual say that when you
On 30/09/2020 6:03 pm, Seymour J Metz wrote:
The DSS manual say that when you specify a directory, it does not dump the
files under that directory. That's very different from the behavior of, e.g.,
tar.
I guess I shouldn't be surprised, given how often IBM don't do things
the way I hoped.
The DSS manual say that when you specify a directory, it does not dump the
files under that directory. That's very different from the behavior of, e.g.,
tar.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
I haven't tested it myself, but what I would hope is that it works like
unix utilities, where the file you specify could actually be a directory.
It is pretty common when using tar etc. to set the working directory,
and specify e.g. "." (a dot) to select the current directory, or specify
a
+1
On 2020-09-30 7:59 AM, Charles Mills wrote:
Applications should not "validate" filenames before attempting to open or
create a file. Present the name to the file system API and report any error back to the
user. Application filename validation is what leads to these inconsistencies.
Wayne: Yes, it does look like each file or path has to be explicitly defined
Paul:
'...akin to asking DFMSMdss to select individual PDS members' is an analogy
I had not seen. Thank you. And of course, DFSMSdss has never been able to
do this and it's unlikely it ever will;
'...filenames containing
42 matches
Mail list logo
