Re: EBCDIC (was: Json table characters)

2018-08-09 Thread Paul Gilmartin
On Thu, 9 Aug 2018 15:14:21 -0400, Tony Harminc wrote:
>
>>>It's worth getting a copy of the SHARE ÆCS report to see what the
>>>state of character encoding and standardization was like in 1989.
>>>
>On 8 August 2018 at 13:03, Paul Gilmartin wrote:
>> Is it available?
>
>I thought I had seen it on Bitsavers, but though there are references
>to it I don't see it there, or indeed anywhere else. Well I have an
>original paper copy, so time to get scanning...
> 
Thanks.  Will it go to Bitsavers?  They do an incredible job of some sort
of 2-layer PDFs which are simultaneously images (even with fingerprints)
and searchable text.  I've found:
https://en.wikipedia.org/wiki/EBCDIC_037
https://en.wikipedia.org/wiki/EBCDIC_037-2
https://en.wikipedia.org/wiki/EBCDIC_1047
Differences in a handful of code points; not enough to bring world
peace or solve climate change.

On Linux, the script below compares the output of "dd conv={ebcdic|ibm}"
to pages 037, 500, and 1047.  The best match seems to be "conv-ibm"
to IBM-1047.

I don't believe that the "dd" utility per se motivated a serious requirement,
but does "dd conv=ibm" reflect otherwise prevalent practice?
(And we still have the LF-NL irritant.)

# #
#! /bin/sh -x

S=$( awk 'BEGIN {
for ( I=32; I<128; I++ ) printf( "%c", I ) }'; )

around() {
echo; echo; echo EBCDIC "$1"
printf %s "$S" | dd conv=ebcdic |
iconv -f "$1" -t ISO8859-1

echo; echo IBM"$1"
printf '%s\n' "$S"
printf %s "$S" | dd conv=ibm|
iconv -f "$1" -t ISO8859-1
}

around CSIBM037
around CSIBM500
around IBM-1047
echo
exit
# #

Thanks again,
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: EBCDIC (was: Json table characters)

2018-08-09 Thread Tony Harminc
On 8 August 2018 at 13:03, Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On Tue, 7 Aug 2018 23:38:07 -0400, Tony Harminc wrote:

>>It's worth getting a copy of the SHARE ÆCS report to see what the
>>state of character encoding and standardization was like in 1989.
>>
> Is it available?

I thought I had seen it on Bitsavers, but though there are references
to it I don't see it there, or indeed anywhere else. Well I have an
original paper copy, so time to get scanning...

Tony H.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: OT - BREXIT parameter in CICS

2018-08-09 Thread Steve Smith
fwiw, it is Friday in Australia, China, and Japan...

I have no idea what the etymology of that CICS version of BREXIT is, but it
occurs to me that it could a synonym of IEFBR14 (BR EXIT), as any program*
launched by the system has R14 pointing at an EXIT SVC.

sas

*except the exceptions, which of course there are legion.


On Thu, Aug 9, 2018 at 10:06 AM, Peter Hunkeler  wrote:

> It is almost Friday.
>
> I'm not a CICS guy, but while looking up something I stumbled across this:
>
>
> From the CICS TS Reference, "Transaction Resources", I just learnt that
> the CICS developers at Hursley long foresaw the UK will leave the EU one
> day or the other: There is a transaction definition parameter called
> BREXIT, and an associated START BREXIT command.
>
>
> LOL. Too cute not to share.
>
>
>
> --
> Peter Hunkeler
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 
sas

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [External] Re: Filemanager and security

2018-08-09 Thread Pommier, Rex
List,

Just a follow-up on this to let those involved in responding to me that I 
didn't forget to reply back, but I got pulled onto more critical issues and 
haven't been able to get back to this.  Once I get it resolved I'll actually 
post what the resolution was - most likely self-inflicted...

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Pommier, Rex
Sent: Wednesday, April 18, 2018 10:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: Filemanager and security

Hey Russell,

I think we're on a different wavelength. :-)  As best I can tell, CA1 is doing 
exactly what it should do.  My comments earlier on the 17 character limit was 
referring to the fact that without a TMS of some flavor, the only thing 
protecting a tape dataset is the DSN on the tape label which can only be 17 
characters, so by necessity that's all the system can check.  My test with 
shorter DSNs was simply taking my 35 (or so) character tape dataset, and trying 
to convince FileManager to let me look at the tape by removing the HLQ of the 
DSN within FM.  CA1 did exactly what I hoped it would do, comparing the DSN the 
TMS said was supposed to be on that tape with what FM was telling CA1 was on 
the tape.  CA1 rightly said the DSNs didn't match and it rejected the tape 
request.  The DSN recorded in CA1 when the tape was created was 
HIGHQUAL.SECONDLQ.MORE.STUFF.G0005V00 (36 characters if I counted right), the 
tape label only has RE.STUFF.G0005V00 on it, so I tried to convince FM to allow 
me to read SECONDLQ.MORE.STUFF.G0005V00 and CA1 said "nope".  

My FM tests were all performed using ISPF so no batch jobs involved, but ISPF 
was displaying the correct DSNs.

FUNC option is set to NO, but I was also telling FM to use SL tapes and not 
BLP.  

Thanks,
Rex

-Original Message-
From: Russell Witt [mailto:res09...@verizon.net] 
Sent: Tuesday, April 17, 2018 8:45 PM
To: 'IBM Mainframe Discussion List' 
Cc: Pommier, Rex 
Subject: RE: [External] Re: Filemanager and security

Rex,

If the DSN is less than 17-characters and CA 1 rejects it; I am wondering if 
Filemanager is dynamically adding an extra HLQ before doing the OPEN and has 
98000 specified to bypass the tape management system. If you look at the job 
that ran successfully, what DSN was actually allocated? Was it the correct name?

And when you say that CA 1 rejects the access when the DSN is less than 
17-characters, what exactly is the rejection message? 

Lastly, is the FUNC option enabled (YES or EXT) within CA 1? This would allow 
you to control who can use 98000 to bypass CA 1.

Russell Witt
CA 1 Development 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Pommier, Rex
Sent: Monday, April 16, 2018 1:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: Filemanager and security

Hi Bob,

Sorry for the delay.  RACF is showing "TAPE DATA SET PROTECTION IS ACTIVE" .  
CA-1 won't allow me to browse the tape using FM if I shrink the DSN or change 
it to something other than what is recorded in TMS.  ICHBLP is defined with 
UACC(NONE) and no users in the access list.  

Thanks,

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Robert S. Hansel (RSH)
Sent: Friday, April 13, 2018 5:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: Filemanager and security

Hi Rex,

How have you activated tape protection in your environment - SETROPTS, 
PARMLIB(DEVSUPxx), or a Tape Management product option? What Tape Management 
product do you have?

Not that this may matter, but does your ID have READ access to FACILITY ICHBLP 
or your Tape Management product's equivalent? If it does, have you tried the 
function with an ID that does not have this access?

Regards, Bob

Robert S. Hansel
Lead RACF Specialist
RSH Consulting, Inc. *** Celebrating our 25th Year ***
617-969-8211
www.linkedin.com/in/roberthansel
https://twitter.com/RSH_RACF
www.rshconsulting.com

-Original Message-
Date:Thu, 12 Apr 2018 13:08:16 +
From:"Pommier, Rex" 
Subject: Re: [External] Re: Filemanager and security

Hi Kolusu,

Unfortunately that doesn't do it.  According to the FileManager documentation - 
which I verified on my system - granting any kind of access (read, update, 
alter, it doesn't matter) either grants you access to the function or denies it 
(access=none).  For example, if I grant READ access to FILEM.TAPE.OUTPUT, I 
have access to update tapes.  Likewise if I grant ALTER access to 
FILEM.TAPE.INPUT, all that gives me access to is tape browse type functions 
like tape browse and tape label display.  These are just toggles to the 
function within FileManager.  The problem that I am running into is that for 
example, if I have 2 production datasets on tape, one with GL information and 
the other with the payroll information on it, and I need 

Re: [External] Re: OSA-ICC ports are disabled

2018-08-09 Thread Jake Anderson
Hi

Thanks All

POR worked plus some chpid Toggle

On Thu 9 Aug, 2018, 6:14 PM Pommier, Rex,  wrote:

> We also just did this literally yesterday!  ICC came up disabled.  Went
> through the same process, plugged the ICC in, loaded the configuration from
> the old machine, and then had to do a POR before it would come up enabled.
>
> One other thing that bit us, we still couldn't get to it from the
> network.  We had to change the port from 3270 to something else.  We chose
> 1024 and then everything started working.  I guess the possible restriction
> is documented at the end of the exception letter but by then my eyes were
> bleary and I missed that note.
>
> Rex
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Michael Babcock
> Sent: Thursday, August 09, 2018 5:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [External] Re: OSA-ICC ports are disabled
>
> We just did this.  Make sure you export your old OSA-ICC config from the
> old HMC and import it to the new one.   Then use Advanced OSA functions,
> card specific functions, and validate and activate.
>
> Once we had our new cable plugged in and the ICC imported and activated, we
> ended up having to do a power on reset to get the card to come active.
>
> One other thing, I’ve heard there was one report of a ZR1 where OSA’s
> wouldn’t work until the OSA cards were reseated by the IBM SSR.
>
> On Thu, Aug 9, 2018 at 2:27 AM Jake Anderson 
> wrote:
>
> > Hi
> >
> > Cross posted .
> >
> > I was able to bring up the z/OS on tht new hardware z14 successfully.
> >
> > The OSA base 1000t were plugged into the correct port as per the chpid
> > mapping output and also the cable was plugged into the correct switch
> port
> >
> >
> > Still the status of the OSA  shows as DISABLED in HMC. I tried with reset
> > too but no luck.
> >
> > Anything that is missing to be checked ?
> >
> > Regards
> > Jake.
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> The information contained in this message is confidential, protected from
> disclosure and may be legally privileged.  If the reader of this message is
> not the intended recipient or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby notified
> that any disclosure, distribution, copying, or any action taken or action
> omitted in reliance on it, is strictly prohibited and may be unlawful.  If
> you have received this communication in error, please notify us immediately
> by replying to this message and destroy the material in its entirety,
> whether in electronic or hard copy format.  Thank you.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


EBCDIC Bad History (was: Json table characters)

2018-08-09 Thread Paul Gilmartin
On 2018-08-09, at 05:18:16, David Crayford wrote:

> On 9/08/2018 2:08 AM, Charles Mills wrote:
>> Yes, ??= is the trigraph for #. Talk about hash!
>> 
>> Trigraphs go away in C++17.
> 
> Michael Wong from IBM has already stated that IBM will still support 
> trigraphs in C++ as an extension. C hasn't deprecated them.
> But seeing as #pragma filetag() is already an extension I see no reason why 
> anybody would use them. I have no idea why
> the health checker header files in SYS1.SIEAHDR.H(HZS*) chose to use them. 
> It's an act of madness!
> 
About 40 years ago, IBM considered Pascal essential:
bitsavers.org/pdf/ibm/370/pascal/SH20-6168-1_VS_PASCAL_Dec81.pdf
Pascal/VS uses square brackets, '[' and ']', in the declaration of arrays.
Because these symbols are not directly available on many I/O devices,
the symbols '(.' and '.)' may be used as an equivalent to square brackets.

I believe the original VM TCP/IP stack (a user developed product) was
written in Pascal.

And IBM devised the dreadful XLATE macro:

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.idar100/g1059.htm
IGC0010CXLATE (translate to and from ASCII (BSAM and QSAM))

I conjecture its primary objective was to map ASCII to code
points supported on existing printers, keyboards, and displays,
but not necessarily with a faithful visual representation.
IIRC, it mapped '[' and ']' to x'4A' and X'5A'.  In CP 037 and
CP 1047 these are  '¢' and '!'.  In CP 500 they are '[' and ']'.
Does anyone recall the chronology?  I imagine bitter internal
territorial fights over the precious code points.

Trigraphs:

https://stackoverflow.com/questions/27601706/c1z-why-not-remove-digraphs-along-with-trigraphs
"C++1z will remove trigraphs. IBM heavily opposed this (here and here)
so there seem to be arguments for both sides of removal/non removal."
citing:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2910.pdf
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4210.pdf

The arguments they raise are:
o Continued support of existing source code relying on trigraphs.
o Support of antique peripheral devices with limited vocabulary.

C/C++ do not use "??" as operators in code.  However, they may
occur in quoted strings and must be converted to support '??/n'
and '??/"'.  for examples.  Supporting them there is not an
extension but a true incompatibility.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [External] Re: OSA-ICC ports are disabled

2018-08-09 Thread Pommier, Rex
We also just did this literally yesterday!  ICC came up disabled.  Went through 
the same process, plugged the ICC in, loaded the configuration from the old 
machine, and then had to do a POR before it would come up enabled.  

One other thing that bit us, we still couldn't get to it from the network.  We 
had to change the port from 3270 to something else.  We chose 1024 and then 
everything started working.  I guess the possible restriction is documented at 
the end of the exception letter but by then my eyes were bleary and I missed 
that note.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Michael Babcock
Sent: Thursday, August 09, 2018 5:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: OSA-ICC ports are disabled

We just did this.  Make sure you export your old OSA-ICC config from the
old HMC and import it to the new one.   Then use Advanced OSA functions,
card specific functions, and validate and activate.

Once we had our new cable plugged in and the ICC imported and activated, we
ended up having to do a power on reset to get the card to come active.

One other thing, I’ve heard there was one report of a ZR1 where OSA’s
wouldn’t work until the OSA cards were reseated by the IBM SSR.

On Thu, Aug 9, 2018 at 2:27 AM Jake Anderson 
wrote:

> Hi
>
> Cross posted .
>
> I was able to bring up the z/OS on tht new hardware z14 successfully.
>
> The OSA base 1000t were plugged into the correct port as per the chpid
> mapping output and also the cable was plugged into the correct switch port
>
>
> Still the status of the OSA  shows as DISABLED in HMC. I tried with reset
> too but no luck.
>
> Anything that is missing to be checked ?
>
> Regards
> Jake.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


OT - BREXIT parameter in CICS

2018-08-09 Thread Peter Hunkeler
It is almost Friday.

I'm not a CICS guy, but while looking up something I stumbled across this:


>From the CICS TS Reference, "Transaction Resources", I just learnt that the 
>CICS developers at Hursley long foresaw the UK will leave the EU one day or 
>the other: There is a transaction definition parameter called BREXIT, and an 
>associated START BREXIT command.


LOL. Too cute not to share.



--
Peter Hunkeler

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: For JES2 Experts - v.2.2 question

2018-08-09 Thread Lizette Koehler
I would go through the Migration Manuals from V1.13 up to V2.2.

As I recall, there are some interesting changes in JES2 Exits over that period
of time.

Also, review if the exit is still needed.  JES2 and other products, have helped
in reducing the number of exits needed.



Lizette


> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of
> Don Parrott
> Sent: Thursday, August 09, 2018 5:17 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: For JES2 Experts - v.2.2 question
> 
> Question: We are trying to reassemble our JES2 exits for z/OS 2.2.In
> z/OS V2R2 can the JES2 JQE still have extensions similar to what is available
> on z/OS 1.13, or is this now somehow prohibited?
> 
> Thanks!
> Don Parrott
> Clemson University
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Jes2 Initiator number

2018-08-09 Thread Greg Price

On 2018-08-08 5:58 AM, Cieri, Anthony wrote:

The audit trail is needed to determine what job(s) instigate the S822 ABENDs.


Well, maybe that audit trail will work now (and maybe it won't)- but it 
definitely would not have been reliable in the past.


In the olden days - even before the iPhone 6 was invented - the JES2 
INIT number was more of a logical concept or a virtual queue - and did 
not mean any particular address space.


For example, suppose the "INIT 2" address space A1 was doing job 
termination.  Then "INIT 2" would be eligible to run a new job.  But 
suppose there were other started initiators that had no work in their 
assigned classes, and so address spaces A2 and A3 were idle initiators.


JES2 may well start the next job under "INIT 2" in address space A2 or 
A3 as JES2 saw fit, perhaps before address space A1 had become truly idle.


S822 abends are probably caused by LSQA fragmentation, where LSQA is 
sloppy terminology for "private high" virtual storage.  If you want to 
find out who the "culprit" is, you need to track the ASID, not the INIT 
number, in my view.


In a previous life as a sysprog, I wrote and implemented an MPF exit to 
append the ASID to the STARTED and ENDED messages - the ones produced by 
the MONITOR or MN command IIRC, but it might also work for the JES2 
messages.  It reported the ASID for started tasks and TSO users as well, 
without actually increasing the number of messages.


You may not be interested in messages as such, but the most convenient 
window into the past I had at the time was the SYSLOG.  If you want to 
look at SMF, then you probably do not need to change much because the 
ASID is in the type 30 (SMF30ASI).


Even if my observations about JES2 INIT numbers are out of date or even 
totally incorrect, ASID is still a valid thing to track when trying to 
track storage fragmentation within the private area of an individual 
address space, so you still don't need to audit JES2 INIT numbers.


And don't forget there is always the el cheapo version of the 
therapeutic IPL - just drain and restart all the initiators every so 
often when convenient for pristine unfragmented private storage for your 
batch jobs.


Cheers,
Greg

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: For JES2 Experts - v.2.2 question

2018-08-09 Thread Allan Staller
I recall having to write some SAPI code for exit 6 circa 2.1 or 2.2 .

Found the info below in the zOS V2.2 Migration Guide. GA32-0889-08

Review changes applicable to JES2 exits
Description: In z/OS V2.1, there may be exit changes necessary, depending on
which exits you are using and which JES2 data areas those exits are referencing.
Element or feature: z/OS JES2.
When change was introduced: z/OS V2R1.
Applies to migration from: z/OS V1R13 and z/OS V1R12.
Timing: Before the first IPL of z/OS V2R1.
Is the migration action required? Yes, if you have any affected JES2 exits.
Target system hardware requirements: None.
Target system software requirements: None.
Other system (coexistence or fallback)
requirements:
None.
Restrictions: None.
System impacts: None.
Related IBM Health Checker for z/OS
check:
None.
Steps to take: Refer to the "JES2 z/OS V2R1 migration details" section of z/OS 
JES2
Installation Exits. This section details the changed information which you may 
need
to accommodate. The changes include (but are not limited to) Exit 6 
considerations,
with the DTE (macro $DTECNV) containing fields which have changed.
Generally, assembly errors in JES2 exits indicate that you were affected by a 
JES2
data area change.
Reference information: z/OS JES2 Installation Exits
JES2 actions to perform after the first IPL of z/OS V2R1
This topic describes JES2 migration actions that you can perform only after you
have IPLed z/OS V2R1. You need a running z/OS V2R1 system to perform these
actions.
None.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Don 
Parrott
Sent: Thursday, August 9, 2018 7:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: For JES2 Experts - v.2.2 question

Question: We are trying to reassemble our JES2 exits for z/OS 2.2.In 
z/OS V2R2 can the JES2 JQE still have extensions similar to what is available 
on z/OS 1.13, or is this now somehow prohibited?

Thanks!
Don Parrott
Clemson University

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::
--
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.
--

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


For JES2 Experts - v.2.2 question

2018-08-09 Thread Don Parrott
Question: We are trying to reassemble our JES2 exits for z/OS 2.2.In 
z/OS V2R2 can the JES2 JQE still have extensions similar to what is available 
on z/OS 1.13, or is this now somehow prohibited?

Thanks! 
Don Parrott
Clemson University

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: EBCDIC (was: Json table characters)

2018-08-09 Thread David Crayford

On 9/08/2018 2:08 AM, Charles Mills wrote:

Yes, ??= is the trigraph for #. Talk about hash!

Trigraphs go away in C++17.


Michael Wong from IBM has already stated that IBM will still support 
trigraphs in C++ as an extension. C hasn't deprecated them.
But seeing as #pragma filetag() is already an extension I see no reason 
why anybody would use them. I have no idea why
the health checker header files in SYS1.SIEAHDR.H(HZS*) chose to use 
them. It's an act of madness!





Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Wednesday, August 8, 2018 10:23 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: EBCDIC (was: Json table characters)

On Wed, 8 Aug 2018 09:55:08 -0700, Charles Mills wrote:


Thank you -- I did not know about not. I see here 
https://en.cppreference.com/w/cpp/language/operator_alternative that there is a 
whole family of these including not_eq.

I have encountered IBM files that used the C++ trigraphs: ??< for { and so 
forth. What an unreadable mess! (IMHO, obviously)


I understand that some compilers have a #pragma that disables trigraphs.
Alas, "#" may not be entirely portable and may need to be coded as a
trigraph.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: OSA-ICC ports are disabled

2018-08-09 Thread Michael Babcock
Jeez, haven’t had my coffee yet, the subject says ICC.   I’ll go back
offline now!

On Thu, Aug 9, 2018 at 5:38 AM Michael Babcock 
wrote:

> I just re-read your post.  No mention of ICC so ignore me!
>
> On Thu, Aug 9, 2018 at 5:36 AM Michael Babcock 
> wrote:
>
>> We just did this.  Make sure you export your old OSA-ICC config from the
>> old HMC and import it to the new one.   Then use Advanced OSA functions,
>> card specific functions, and validate and activate.
>>
>> Once we had our new cable plugged in and the ICC imported and activated,
>> we ended up having to do a power on reset to get the card to come active.
>>
>>
>> One other thing, I’ve heard there was one report of a ZR1 where OSA’s
>> wouldn’t work until the OSA cards were reseated by the IBM SSR.
>>
>> On Thu, Aug 9, 2018 at 2:27 AM Jake Anderson 
>> wrote:
>>
>>> Hi
>>>
>>> Cross posted .
>>>
>>> I was able to bring up the z/OS on tht new hardware z14 successfully.
>>>
>>> The OSA base 1000t were plugged into the correct port as per the chpid
>>> mapping output and also the cable was plugged into the correct switch
>>> port
>>>
>>>
>>> Still the status of the OSA  shows as DISABLED in HMC. I tried with reset
>>> too but no luck.
>>>
>>> Anything that is missing to be checked ?
>>>
>>> Regards
>>> Jake.
>>>
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>
>>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: OSA-ICC ports are disabled

2018-08-09 Thread Michael Babcock
I just re-read your post.  No mention of ICC so ignore me!

On Thu, Aug 9, 2018 at 5:36 AM Michael Babcock 
wrote:

> We just did this.  Make sure you export your old OSA-ICC config from the
> old HMC and import it to the new one.   Then use Advanced OSA functions,
> card specific functions, and validate and activate.
>
> Once we had our new cable plugged in and the ICC imported and activated,
> we ended up having to do a power on reset to get the card to come active.
>
>
> One other thing, I’ve heard there was one report of a ZR1 where OSA’s
> wouldn’t work until the OSA cards were reseated by the IBM SSR.
>
> On Thu, Aug 9, 2018 at 2:27 AM Jake Anderson 
> wrote:
>
>> Hi
>>
>> Cross posted .
>>
>> I was able to bring up the z/OS on tht new hardware z14 successfully.
>>
>> The OSA base 1000t were plugged into the correct port as per the chpid
>> mapping output and also the cable was plugged into the correct switch port
>>
>>
>> Still the status of the OSA  shows as DISABLED in HMC. I tried with reset
>> too but no luck.
>>
>> Anything that is missing to be checked ?
>>
>> Regards
>> Jake.
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: OSA-ICC ports are disabled

2018-08-09 Thread Michael Babcock
We just did this.  Make sure you export your old OSA-ICC config from the
old HMC and import it to the new one.   Then use Advanced OSA functions,
card specific functions, and validate and activate.

Once we had our new cable plugged in and the ICC imported and activated, we
ended up having to do a power on reset to get the card to come active.

One other thing, I’ve heard there was one report of a ZR1 where OSA’s
wouldn’t work until the OSA cards were reseated by the IBM SSR.

On Thu, Aug 9, 2018 at 2:27 AM Jake Anderson 
wrote:

> Hi
>
> Cross posted .
>
> I was able to bring up the z/OS on tht new hardware z14 successfully.
>
> The OSA base 1000t were plugged into the correct port as per the chpid
> mapping output and also the cable was plugged into the correct switch port
>
>
> Still the status of the OSA  shows as DISABLED in HMC. I tried with reset
> too but no luck.
>
> Anything that is missing to be checked ?
>
> Regards
> Jake.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


OSA-ICC ports are disabled

2018-08-09 Thread Jake Anderson
Hi

Cross posted .

I was able to bring up the z/OS on tht new hardware z14 successfully.

The OSA base 1000t were plugged into the correct port as per the chpid
mapping output and also the cable was plugged into the correct switch port


Still the status of the OSA  shows as DISABLED in HMC. I tried with reset
too but no luck.

Anything that is missing to be checked ?

Regards
Jake.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN