Curiosity/Impact questions
PROGxx has existed for almost 25 years, and support within there for
dynamic LNKLST for almost 20 years.
We're looking at some new work for which we likely won't change the
LNKLSTxx path, thus requiring use of PROGxx for defining the LNKLST in
order to use the new
-- are (we) still using LNKLSTxx - No.
Are (we) using a dynamically format APF list? - Yes.
Kees.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Peter Relson
Sent: 11 December, 2014 14:12
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: PROGxx
Peter Relson wrote:
PROGxx has existed for almost 25 years, and support within there for dynamic
LNKLST for almost 20 years.
Too long. Haha ;-D
We're looking at some new work for which we likely won't change the LNKLSTxx
path, thus requiring use of PROGxx for defining the LNKLST in order to
On 12/10/2014 10:45 PM, Alan Watthey wrote:
David,
Yes, this function works perfectly for me. You need to use R or RC in front of
what you are finding or changing (first parameter).
You have to learn regular expressions of course which can be a bit mind blowing
but knowing PERL helps in my
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Alan Watthey
Sent: Wednesday, December 10, 2014 11:45 PM
David,
Yes, this function works perfectly for me. You need to use R or RC in front
of what you are finding
or changing (first parameter).
You have to
On 2014-12-10 17:48, Charles Mills wrote:
Question: Does the use of aliases make sense? Let's say HLQ.BAR is
identical across A, B and C. Should I make one HLQ.BAR.COMMON and
alias it as .A, .B and .C? Or is that overkill for a simple one-person
situation? Should I just make three
Chase, John wrote:
I love this new feature because I can now change lower case to lower case
and upper case to upper case separately in files.
Having a brain cramp If you change lower case to lower case, what gets
changed? Same question for upper case to upper case.
Uh-oh. This is a
I took that to mean that he can change lower case data independent of upper
case data, even if the text strings might be similar. For example, changing
ftp.mynode.somthing to ftp.newnode.something without also changing
DSN=DATAFOR.MYNODE.TRANSMIT,DISP=SHR
Billy
On Thu, Dec 11, 2014 at 9:19 AM,
APF format Dynamic,
LNKLSTxx - not in use (for at least 10 years)
HTH,
snip
PROGxx has existed for almost 25 years, and support within there for dynamic
LNKLST for almost 20 years.
We're looking at some new work for which we likely won't change the LNKLSTxx
path, thus requiring use of PROGxx
Here comes my $0.02 worth.
You can use the DEFINE ALIAS with NAME (the alias name HLQ.BAR.COMMON) and
SYMBOLICRELATE the actual data set name, but with a SYSTEM SYMBOL in it,
HLQ.BAR.BB, or even, HLQ.FOOBAR..BARFOO where FOOBAR=FOO or BAR and
BARFOO = A,B,C.
See DFSMS Managing Catalogs for
Peter,
We don't use the LNKLSTxx any longer.
We do use Dynamic APF list through the PROGxx member.
Roy
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Peter Relson
Sent: Thursday, December 11, 2014 8:12 AM
To:
Hi Kees,
sorry, there is no way to classify based on the existence/specification of a
work qualifier.
On z/OS V2.1 you could simplify your rules by creating a scheduling environment
group but it would still require that the group specification includes all your
scheduling environments.
Horst
Bill Ashton wrote:
I took that to mean that he can change lower case data independent of upper
case data, even if the text strings might be similar. For example, changing
ftp.mynode.somthing to ftp.newnode.something without also changing
DSN=DATAFOR.MYNODE.TRANSMIT,DISP=SHR
If so, that can be
On Thu, 11 Dec 2014 08:39:23 -0600, Elardus Engelbrecht wrote:
Bill Ashton wrote:
I took that to mean that he can change lower case data independent of upper
case data, even if the text strings might be similar. For example, changing
ftp.mynode.somthing to ftp.newnode.something without also
W dniu 2014-12-11 o 14:11, Peter Relson pisze:
Curiosity/Impact questions
[...]
Do you really expect a reason except plain reluctance to change?
--
Radoslaw Skorupka
Lodz, Poland
--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku
przeznaczone wycznie do uytku
$PO JQ,JM=IDCDEFR*,ALL,CC=(4)
$HASP003 RC=(82),PO JQ CC 4 - INVALID FILTER KEYWORD
$PO JQ,JM=IDCDEFR*,CC=4
$HASP003 RC=(82),PO JQ CC 4 - INVALID FILTER KEYWORD
$PO JQ,JM=IDCDEFR*,ALL
$HASP686 OUTPUT(IDCDEFR5) OUTGRP=1.1.1 CANCELLED
$HASP686 OUTPUT(IDCDEFR5) OUTGRP=1.1.1 CANCELLED
$HASP686
are folks still using LNKLSTxx? Nope
Dana
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
On 12/11/2014 8:01 AM, Paul Gilmartin wrote:
On Thu, 11 Dec 2014 08:39:23 -0600, Elardus Engelbrecht wrote:
Bill Ashton wrote:
I took that to mean that he can change lower case data independent of upper case data, even if the
text strings might be similar. For example, changing
On 12/11/2014 8:12 AM, Peter Relson wrote:
Curiosity/Impact questions
PROGxx has existed for almost 25 years, and support within there for
dynamic LNKLST for almost 20 years.
We're looking at some new work for which we likely won't change the
LNKLSTxx path, thus requiring use of PROGxx for
I still see sites using LNKLSTxx, but I don't see sites using IEAAPFxx
anymore. As far as why, if it ain't broke, don't fix it. A statement
from IBM that LNKLSTxx is deprecated could incentivize the switch. Can
you write a health check to encourage conversion from LNKLSTxx to PROGxx?
We're
You can use the IEASYMUP module provided in SYS1.SAMPLIB or the SYMUPDTE
routine to update system symbols which update in place. Then just cycle the
task using SYMBOLICRELATE.
I did this for a lot of 3rd party vendor software that was off the sysres.
Lizette
-Original Message-
From:
T is still documented in the ISPF help:
A text string is used to find a character string regardless of whether
alphabetic characters are upper or lower case.
Example - === find
Hi, I agree that it just sounds like your CDSes have just grown and need more
space. Please note that the CA Reclaim function became available in V1R12.
When CA Reclaim is enabled for the CDSes, it minimizes the need to reorganize
the CDSes, especially after running EXPIREBV. When a VSAM
Thanks, last night, I ran my BCDS up close to the limit on a non-SMS Mod-9. I
still find the change in behavior correlates well with z/OS 1.13
CA Reclaim is a new feature I had not noticed. Since it is turned off by
default, I now need to ask:
Is there any reason not to turn it on?
Yes. For the exact problem you are currently encountering!
snip
CA Reclaim is a new feature I had not noticed. Since it is turned off by
default, I now need to ask:
Is there any reason not to turn it on?
/snip
--
For
Hi, List,
I set a SLIP IF trap that included DATA=(0R,EQ,0,AND,12R,EQ,25BD8),ID=ID01.
The response to a D SLIP=ID01 command shows
DATA=0,0R,EQ,,AND,12R,EQ,00025BD8 .
Where did that leading zero immediately after the DATA= come from? I deleted
and reset the SLIP, and the leading zero
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Chase, John
Sent: Thursday, December 11, 2014 2:29 PM
Hi, List,
I set a SLIP IF trap that included DATA=(0R,EQ,0,AND,12R,EQ,25BD8),ID=ID01.
The response to a D SLIP=ID01
I asked for reasons to NOT turn it on.
As to my specific problem, there is a caveat in the documentation than
indicates it isn't an immediate solution.
CA's that are empty when CA Reclaim is enabled are not reclaimed.
So, I would have needed to delete/reallocate my xCDS(s) anyway.
The same
There might be some slight performance impact, and also check for any
missing maintenance. That being said, we've had it turned on since zOS
1.12 and it's never caused a problem.
Mark Jacobs
Gibney, Dave wrote:
I asked for reasons to NOT turn it on.
As to my specific problem, there is a
Caveat: insert Daily Digest delay here...
Mike: in support of Lizette's response, I'll add that we've been running the
following JES2 command daily for the last 5+ years (z/OS v1.7? v1.4?). (VS is
the ESP command to execute a console command.) You should be able to adjust
accordingly.
mark.jac...@custserv.com (Mark Jacobs) wrote:
There might be some slight performance impact, and also check for any
missing maintenance. That being said, we've had it turned on since zOS
1.12 and it's never caused a problem.
snip
I am not a VSAM expert, and I didn't stay in a hotel of any
Caveat: insert Daily Digest delay here...
Charles: in addition to gil's notes [1], be advised that {any, some} catalogue
changes to .COMMON will lose all the aliases. For example, I have daily
processing to create FDR exclusion commands for all aliases in the system [2]
that are included in
I can think of no reason not to turn it on.
I have had it turned it for *all* VSAM processing (including user catalogs)
since early 2012 w/no reported issues.
I would turn it on prior to rebuilding the CDS's/UCATS and then proceed with
whatever is necessary.
HTH,
snip
I asked for reasons to
W dniu 2014-12-11 o 22:12, Neil Duffee pisze:
Caveat: insert Daily Digest delay here...
Charles: in addition to gil's notes [1], be advised that {any, some} catalogue
changes to .COMMON will lose all the aliases. For example, I have daily
processing to create FDR exclusion commands for all
CA_RECLAIM() parm on IGDSMSxx
check this out:
There might be a difference between the z/OS and Linux in processing
updates to an aliased file.
On Linux, if you update any of the file names, the new copy gets a new
storage location. The old location goes away when all pointers to it
have been updated to new locations.
On z/OS, any update gets
Thank you all. I have decided to just make multiple copies and skip the
aliases. I think I was an engineer with a solution in search of a problem.
The killer was symbolic substitution. If I do copies in JCL I can use JCL
set symbols in an INCLUDEd member. To use IDCAMS I would have to use system
On Thu, 11 Dec 2014 15:35:08 -0800, Charles Mills wrote:
You can't have an alias of an alias
I can see the analogy to PDSes. Only members can have aliases; aliases can't
have aliases, right?
Gee. No matter how bad something is, if you can find something equally
bad or worse to compare it to,
I did a double DUH! when I saw the missing R reply. It wasn't quite that bad.I
cannot cut/paste the brackets []
from/to or to/from my Reflections for IBM 3270 emulator session. Had to FTP
them into my TSO/PDS and ofcourse key them into the
question. The Find command
On 2014-12-11 08:57, Grinsell, Don wrote:
T is still documented in the ISPF help:
I couldn't find in the ISPF Ref. Either the Ref. is more proactive
in weeding out obsolescent constructs ('t' merely asserts the default),
or I didn't look hard enough.
A text string is used to find a character
On 12/12/2014 11:38 AM, David Speake wrote:
I did a double DUH! when I saw the missing R reply. It wasn't quite that bad.I
cannot cut/paste the brackets []
from/to or to/from my Reflections for IBM 3270 emulator session. Had to FTP
them into my TSO/PDS and ofcourse
On Thu, Dec 11, 2014 at 9:38 PM, David Speake david.spe...@bcbssc.com
wrote:
I did a double DUH! when I saw the missing R reply. It wasn't quite that
bad.I cannot cut/paste the brackets []
from/to or to/from my Reflections for IBM 3270 emulator session. Had to
FTP them into my TSO/PDS and of
On Dec 11, 2014, at 7:11 AM, Peter Relson wrote:
Curiosity/Impact questions
PROGxx has existed for almost 25 years, and support within there for
dynamic LNKLST for almost 20 years.
We're looking at some new work for which we likely won't change the
LNKLSTxx path, thus requiring use of PROGxx
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of David Crayford
Sent: Thursday, December 11, 2014 10:08 PM
On 12/12/2014 11:38 AM, David Speake wrote:
I did a double DUH! when I saw the missing R reply. It wasn't quite that
bad.I cannot cut/paste the
brackets
44 matches
Mail list logo
