Thanks to those that offered help (some were offline).
When I set the code page of the OMVS terminal, it works
f.cvtcmd = SETAUTOCVTON ;
f.fccsid = 0x0417 ; // set this
f.pccsid = 0x ; // ignore this
* rc =fcntl( STDOUT_FILENO,action, &f ); *
it works.
Before Python the filetag(fcc
Hi,
Does anyone have information on an upgrade path from a Z13s to a Z16.
Many thanks in advance,
Charles.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message
Start by going to a z15 8562 T02 (available today).
Negotiate that as part of your upgrade to the smaller z16 once IBM makes it
available.
On Fri, Aug 19, 2022 at 5:00 AM Charles MacNiven <
0325e5af57fe-dmarc-requ...@listserv.ua.edu> wrote:
> Hi,
> Does anyone have information on an upgrade p
Would anyone know what produces diag data such as jobname owner job id when
using IARV64 REQUEST=LIST
Since you presumably don't want the correct but snarky answer of "yes", and you
probably don't want the answer of "RSM code", please re-phrase your question.
What is it that you want to know?
Well, the obvious answer, chcp isn't allowed under he TSO/E OMVS command. What
about changing the locale?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Colin Paice [c
thanks Mike, that is what the team is suggesting, hopefully they will
make a decision before the z15 is EOL :(
historically that's how long it takes leadership to act
Carmen
On 8/18/2022 11:31 PM, Mike Schwab wrote:
Ask them for a price quote on a used z15.
On Thu, Aug 18, 2022, 14:53 Carmen
Peter
The documentation says
That if the x’04’ bit or V64DIAGDATA bit of V64WAFLAG1 in a entry or in
V64WAENTRY is
on then the V64WADIAGDATA structure would follow
The V64WAENTRY entry
My question is what would produce the additional diag data
In addition looking at the diag data I see a
22219 03:28:57.34 STC46322 0281 IEF234E K 120B,VP0597,PVT,HZSPROC,HZSSTEP
- RACK=VP0597
22219 03:28:57.36 STC46322 0090 HZS0001I CHECK(IBMCSV,CSV_LNKLST_SPACE):
071
22219 03:28:57.55 STC46322 0090 HZS0001I CHECK(IBMCSV,CSV_APF_EXISTS): 072
Based on the presence of the messages b
Hi
Is it possible to activate only one health checker via HZSPRM? As I am
trying to activate only IEA_,ASID but along with that other policy are too
get activated.
Any suggestions on how to proceed?
Peter
--
For IBM-MAIN subscr
There isn't one. The only announced upgrade paths are from z14 and z15.
Normally there isn't an upgrade path from the baby z to its big brother.
Suggest you talk to IBM sales for a possible 'upgrade' via a supported upgrade.
Regards
Parwez Hamid
From: IBM Mainf
I have turned on DYNAMIC dumps and tested.
No I want to drop my PHYSICAL dump datasets. That is easy.
What do I need to do in PARMLIB to insure the system doesn't
Look for them after I delete the PHYSICAL dump datasets?
TIA
Steve
--
I still keep mine around just in case, the very rare instance I get an
SVC dump before SMS, very doubtful but it does not affect anything, take
any more resources
I'd show you my parms..but right now our entire network is down, so it's
a bad Friday for our network folks
Carmen
On 8/19/2022
I specify DUMP=NO,
sorry Steve, I neglected to say that, but I didn't delete my SYS1.DUMP
datasets
Carmen
On 8/19/2022 9:12 AM, Steve Beaver wrote:
I have turned on DYNAMIC dumps and tested.
No I want to drop my PHYSICAL dump datasets. That is easy.
What do I need to do in PARML
I have turned on DYNAMIC dumps and tested it.
Now I want to drop my PHYSICAL dump datasets. That is easy.
Real Question : Do I just delete the datasets to insure the system doesn't
find them?
TIA
Steve
--
Hi Steve, I'll try and respond to you again, IIRC you cannot just delete
the dump datasets, you need to specify DUMP=NONE in the IEASYS00 member
use the DUMPDS in COMMND00 as you did to activate the dynamic allocation
of dumps.
as I said before, I opted not to remove the dump datasets or chan
Hello,
A couple of questions I had in email, which I hope will help here:
I was asked about if a COLD START was required in z/OS V2.5: There is NO COLD
START required for z/OS V2.5. I haven’t seen a required COLD start, in like
forever, and I can’t recall that we have needed it during my who
for me moving from 2.3 to 2.4, (I waiting some time to upgrade to Z22
mode) , I have to enlarge my CKPT datasets then $ACTIVATE,LEVEL=Z22
you can $DACTIVATE to check if your current CKPT's meet the requirements.
I performed the CKPT change using the checkpoint dialog to move to
newckpt1 and 2
That's what I had to do too. Fortunately, it was a small system, and a cold
start was no big deal. I could have used the CKPT reconfig dialog. But it was
easier for me to allocate new CKPT datasets, IPL, and COLD start with the new
CKPT datasets.
Sent with Proton Mail secure email.
-
18 matches
Mail list logo
