It might be helpful to run a batch listcat on the files and then sort the
output on the field LADAT(Last Alter Date) and then run IDCAMS Delete File and
Delete GDG on all that are older than a required date. This could be done on
other GDG's to clean up all junk GDG's.
David Mingee
Not sure how to take this comment...
Define quality.
Darren
On Mon, 22 Feb 2016, Ed Gould wrote:
>Agreed, ever since Darren "retired" the quality of the list has
>declined.
>
>
>Ed
>On Feb 21, 2016, at 6:10 PM, Joel C. Ewing wrote:
>
On 22/02/2016 9:52 AM, Charles Mills wrote:
Although I think now they have co-located their servers at Sonic or someone
like that. Part of the reason, IIRC, is that their building is not real
rain-tight, and it rains a lot here in the Emerald Triangle.
Why is it called the Emerald Triangle?
Agreed, ever since Darren "retired" the quality of the list has
declined.
Ed
On Feb 21, 2016, at 6:10 PM, Joel C. Ewing wrote:
SNIP-
--
For IBM-MAIN subscribe /
Bruce Hewson wrote:
>I forgot to add in my previous post:-
>Once you have IPL'd your system, THEN TAKE THAT DASD VOLUME OFFLINE!
Or take it down from another LPAR while your problem system is down.
I see this thread is about a very messy *weekend* problem which could be
avoided in the first
I forgot to add in my previous post:-
Once you have IPL'd your system, THEN TAKE THAT DASD VOLUME OFFLINE!
Regard
Bruce
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu
WARNING!
The original post:-
IBM Mainframe Discussion List
Date:
Sat, 20 Feb 2016 16:36:30 +0530
Hello,
One of my dasd device not going offline. I tried all possible way
but still not success. I am not able to find, who is holding this device.
We are
Darren, thanks! Any idea what the root problem is? Here is the original note
to John:
We have had problems with our mail server resolving the DNS for your list
server ibm-main@listserv.ua.edu. I contacted the UA IT help desk and they
said you were the list manager and I should direct my question
Let's not start inundating John Watters with emails about IBM-MAIN. I know
John and worked with him my entire career at UA. He was my manager most of
that time. I think the Helpdesk misrouted the problem to him. He has
nothing to do with Listserv. I will contact him.
Darren
On Sun, 21 Feb
Jack J. Woehr wrote:
I'm assuming it's the "too often" problem There are other problems, e.g., intermittent misconfiguration of the request
to uribl.com that could cause uribl.com to refuse the request.
Another possibility ... I like this one ... is that your mail server is s-l-o-w to respond
Charles Mills wrote:
I sent this once already but it seems to have disappeared entirely --
neither posted nor bounced.
I halfway "get" DNS and SMTP and all that but I am not sufficiently an
expert to debate with someone who thinks they are. Here is the server log
supplied by my ISP for one of
I halfway "get" DNS and SMTP and all that but I am not sufficiently an
expert to debate with someone who thinks they are. Here is the server log
supplied by my ISP for one of the bounces:
Feb 20 10:51:42 mailfe qmail: 1455994302.150110 new msg 393337
(faf14e4e-d802-11e5-9c96-00505681fcd5)
Feb 20
I sent this once already but it seems to have disappeared entirely --
neither posted nor bounced.
I halfway "get" DNS and SMTP and all that but I am not sufficiently an
expert to debate with someone who thinks they are. Here is the server log
supplied by my ISP for one of the bounces:
Feb 20
Would make a great star trek episode ...
The trouble with URIBLS
Chris Hoelscher
Technology Architect, Database Infrastructure Services
Technology Solution Services
: humana.com
123 East Main Street
Louisville, KY 40202
Humana.com
(502) 714-8615, (502) 476-2538
> -Original Message-
Charles Mills wrote:
Seven greens and three yellows. I don't think it is a SPAM filter problem --
the server logs indicate it is a DNS problem.
Apparently UA is using URIBL to scope you out and botching the job.
--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
Seven greens and three yellows. I don't think it is a SPAM filter problem --
the server logs indicate it is a DNS problem.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jack J. Woehr
Sent: Sunday, February 21, 2016 4:35 PM
My mistake, it's more subtle than that. UA's reverse lookup of your address was
blocked.
"If an email you sent bounced, and included a link to this page, then it was rejected because the receiver has not
implemented URIBL lookups correctly. URIBL uses bitmask responses to indicate a domain
CM Poncelet wrote:
These are the headers (starting from the bottom upwards), if it helps.
X-Gwh-Spam-Flags:
BAYES_00,FROM_LOCAL_HEX,FROM_STARTS_WITH_NUMS,RCVD_IN_DNSWL_LOW,URIBL_BLOCKED
"URIBL_BLOCKED"
Your server won't reply to a reverse DNS query so it's scoring high on the spam
meter.
On Sun, 21 Feb 2016 11:42:58 -0800, Charles Mills wrote:
>
>>1. Is anyone else getting occasional bounces when posting to IBMMAIN?
Charles could test his outgoing server on
http://www.allaboutspam.com/email-server-test/
--
Jack J. Woehr # Science is more than a body of knowledge. It's a
000a2a8c2020-dmarc-requ...@listserv.ua.edu (Tom Marchant) writes:
> ASCII was seriously considered for the initial System/360
> design. Amdahl, Blaauw and Brooks published an article in the IBM
> Journal in April, 1964, titled "Architecture of the System/360" in
> which many of the design
These are the headers (starting from the bottom upwards), if it helps.
helo=inbound-queue-2.mail.thdo.gradwell.net country=GB) by
gwh-1.gradwell.net with esmtp (Gradwell gwh-smtpd 1.290) id 56ca28bc.6417.0
for ponce...@bcs.org.uk; Sun, 21 Feb 2016 21:14:36 +
Maybe if a few of us forward this post to Mr. Waters he will realize that the
list is
still active. Then again, maybe he'll make sure that it is shut down.
On Sun, 21 Feb 2016 11:42:58 -0800, Charles Mills wrote:
>1. Is anyone else getting occasional bounces when posting to IBMMAIN? I have
1. Is anyone else getting occasional bounces when posting to IBMMAIN? I have
started getting them sometimes. A retry sometimes produces another bounce;
eventually the post goes through, obviously.
2. I am on a small rural ISP. They do not have a roomful of high-powered
engineers. They recently
>From what I have read in IBM APAR's and PTF's, the OPTCD=B trick should do the
>job. However, that does NOT take into account dynamic allocation. Or, it might
>be possible that the COBOL program itself is over-riding the DCB parameters
>and basically turning OPTCD=B off. I believe I can workup
> >LNKLST UPDATE JOB(*)
> And you should never use LNKLST UPDATE unless you are willing to re-IPL
at
> the next instant, as it is unpredictably dangerous. Of course sometimes
> that is better than not trying it at all.
And if you do use LNKLST UPDATE and you are on a release older than
z/OS
The error is clear. When you first IPL'd the catalog for the four datasets you
name pointed to a specific volume. You recataloged them using the exact same
name to volume ** which does not match the volume the ACTIVE LNKLST has for
them. I have found that the LNKLST does not like
Hi Russell,
Sorry, I thought Chris kept you in the loop.
He said he tried it and it didn't work.
A little too trusting here. He was tied up Friday
and I have not 'seen with my own eyes'.
Had time myself so I went to reading and experimenting.
Put it on hold till I do see it myself.
Chris is
Never meant to suggest that going backwards was the direction I desired.
Simply stating that having a few weird features can be a good thing when
struck with a production issue, service level agreements and (insert "other
institution specific intractable" here).
Ideally, it would be great to have
Answers for the query raised.
1) Is this a production or TEST or DEV environment where this problem is
occurring?
Ans : This is production system.
a) How long can this system be unusable? If not much longer, open an
SR to IBM for assistance.
Ans : If this
2) When you recataloged the datasets
On Sun, 21 Feb 2016 11:22:17 +0530, Mainframe Mainframe wrote:
>When I am trying to runSETPROG LNKLST,ALLOCATE command , I am
> getting below error on console,
>
>CSV540E LNKLST SET LNKLST00 is in error.
> DATASET SET SYS1.SERBLINK
> HAS VOLUME ID DOESNT NOT MATCH WITH CATALOG.
There is a
The simple "fix" is to code the OPTCD=B parameter in the JCL. With the OPTCD=B
coded, then z/OS does not care if volume 3 is open'ed before volume's 1 & 2 and
does not care if EOV is reached before EOF. It simply reverts back to the way
z/OS operated prior to z/OS 1.13 when the new feature was
Charles Mills wrote:
> http://bitsavers.trailing-edge.com/pdf/ibm/360/princOps/A22-6821-0_360PrincOps.pdf
>
> Too wonderful for words!168 pages for the whole book...
Indeed! I keep a saved copy on my desktop and sometimes still reference it for
sake of simplicity.
> It's an image scan and
Hello Lizette,
I checked master catalog entry and
NONVSAM --- SYS1.SERBLINK
HISTORY
DATASET-OWNER-(NULL) CREATION2016.051
RELEASE2 EXPIRATION--.000
VOLUMES
VOLSER**
Regarding
SETPROG LNKLST,UNALLOCATE
P LLA
SET PROG=09
S LLA,SUB=MSTR
SETPROG LNKLST,ALLOCATE
This approach is not right. It is either unnecessary or wrong. LNKLST
UNALLOCATE is provided so that you can manipulate an uncataloged data set
of the same name
The list cannot replace a vendor support function.
This message: CSV540E LNKLST SET LNKLST00 is in error.
DATASET SET SYS1.SERBLINK
HAS VOLUME ID DOESNT NOT MATCH WITH CATALOG.
Is telling you exactly what is wrong. The linklist entry and the catalog entry
do
On Saturday, 20 February 2016 16:46:14 UTC, Paul Gilmartin wrote:
> On Sat, 20 Feb 2016 06:54:56 -0600, Bill Woodger wrote:
A COBOL program can establish its own collating sequence, which can be
user-defined or "ASCII" or...
This would only affect alphanumeric fields (OK, I'll assume PIC A as
I think you're going to need to show the code. It is unclear to me what you are
doing, and why you are doing it, and what outcome you expect.
Which compiler are you using?
If you have an active exit which prevents you reading a single volume from a
multi-volume dataset, I strongly doubt that
37 matches
Mail list logo