Re: Determine if running under Secondary Subsystem

[Vernooij, Kees (ITOP NM) - KLM]

The answers given so far imply that you know the names of the primary/secondary 
subsystems and from that determine under which you run.
As far as I remember, there is a pointer to *the* subsystem, which is the 
primary subsystem. I can't dig up where that pointer is.

Kees

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Szura
Sent: 07 February 2020 21:37
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Determine if running under Secondary Subsystem

Is there a way to tell if you application is running under a Secondary 
JES?  We have common code that is used in several products that needs to 
check the JES it is running under.  If I look at the chain of SSCTs it 
will only tell me there are more than one JES running but I can't find a 
way to determine under which the application started.

j

-- 
John Szura
Lead Mainframe Product Developer
Tone Software Corp.
+1(714)507-2354

  IMPORTANT NOTICE:

This is a private message. The information in this email (including any 
attachments) is confidential and proprietary to Tone Software
Corporation, and is provided solely for the use of the individual or entity to 
which it is addressed. Any review, reliance upon, printing,
distribution, or forwarding without express permission of its sender is 
strictly prohibited. If you are not its intended recipient, please
immediately delete this email without copying and kindly advise me by email of 
the mistaken delivery.

  

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

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286



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

Re: Phases of Project in Mainframe

[Alan Young]

This Redbook looks similar to that z10 SAPR document. It is for a z13.

Mainframe from Scratch: Hardware Configuration and z/OS Build
http://www.redbooks.ibm.com/abstracts/sg248329.html

-Original Message-
>From: Edward Finnell <000248cce9f3-dmarc-requ...@listserv.ua.edu>
>Sent: Feb 9, 2020 8:29 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Phases of Project in Mainframe
>
>The latest SAPR I could find was for a Z10. Supposedly it all falls out with 
>Workflow from OSMF but don't think you get the detail.
>
>https://wiki.enterpriselab.ch/el/_media/mainframe:documentation:ibm_2097_z10_sapr_guide_tda_sa06-016-11.pdf

In a message dated 2/9/2020 9:21:28 PM Central Standard Time, 
idfli...@gmail.com writes:
>for me , I need more information so i can see all the pieces
>of a project, IMHO
>
>--
>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: UTF16 to EBCDIC

[Mike Schwab]

EBCDIC, EBCDIC DBCS, UTF-16, and ASCII all require the user to know
the code page for the data set.  UTF-8 uses up to 32 bits and
incorporates all languages include several DBCS languages from Asia.

On Sun, Feb 9, 2020 at 10:07 PM Edward Finnell
<000248cce9f3-dmarc-requ...@listserv.ua.edu> wrote:
>
> Guess I don't see the reasoning. IBM has had DBCS for decades.
>
> http://www-01.ibm.com/support/docview.wss?uid=swg27004197=1In a message 
> dated 2/9/2020 9:58:05 PM Central Standard Time, li...@akphs.com writes:
> Gil corrected me:
> > You're describing UTF-8.  UTF-16 uses 16-bit code units.>
> >  https://en.wikipedia.org/wiki/UTF-16
>
>
> Jeez, yes, of course. Brainfart! Thanks.
>
> --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



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: UTF16 to EBCDIC

[Paul Gilmartin]

On Mon, 10 Feb 2020 04:06:35 +, Edward Finnell < wrote:

>Guess I don't see the reasoning. IBM has had DBCS for decades.
>
>http://www-01.ibm.com/support/docview.wss?uid=swg27004197=1In
ITYM:
 http://www-01.ibm.com/support/docview.wss?uid=swg27004197=1

UTF-8 has enormous compatibility with ASCII.  IBM DBCS has such
compatibility neither with EBCDIC nor with ASCII.  On Linux or MacOS
I can code C source programs or shell scripts alike in ASCII or UTF-8.
Can COBOL or HLASM source, or JCL be DBCS?

-- gil

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

Re: UTF16 to EBCDIC

[Paul Gilmartin]

On Mon, 10 Feb 2020 04:06:35 +, Edward Finnell < wrote:

>Guess I don't see the reasoning. IBM has had DBCS for decades.
>
>http://www-01.ibm.com/support/docview.wss?uid=swg27004197=1In
ITYM:
 http://www-01.ibm.com/support/docview.wss?uid=swg27004197=1


>> You're describing UTF-8.  UTF-16 uses 16-bit code units.>    
>>  https://en.wikipedia.org/wiki/UTF-16
>
>
>Jeez, yes, of course. Brainfart! Thanks.
>
>--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

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

Re: UTF16 to EBCDIC

[Steve Smith]

*ALL* talk about Unicode is dangerous ;-).  Your description is of UTF-8,
which can use 1, 2, 3, or 4 bytes per character, while UTF-16 uses only
either 2 or 4.  Both are variable-length encoding, although the variability
of UTF-16 is... strange.

sas


On Sun, Feb 9, 2020 at 9:51 PM Phil Smith III  wrote:

> Mike Schwab wrote:
>
> >Would UTF-16 to UTF-8 be a better conversion?  You still have to be
>
> >certain of the source character set.  And is supported by some z/OS
>
> >software.
>
>
>
> As Cameron indicated, your comment doesn't quite make sense. UTF-16 is
> just a variable-length encoding, in which basic ASCII*
> (0-127) are single-byte, some characters are two-byte, some three-, and
> some four-. More efficient, especially in the "mostly basic
> ASCII" case.
>
>
>
> *Yes, I know, talking about "ASCII" in the context of Unicode is dangerous
> and arguably incorrect. You know what I mean.
>
>
> --
> 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: UTF16 to EBCDIC

[Edward Finnell]

Guess I don't see the reasoning. IBM has had DBCS for decades.

http://www-01.ibm.com/support/docview.wss?uid=swg27004197=1In a message 
dated 2/9/2020 9:58:05 PM Central Standard Time, li...@akphs.com writes:
Gil corrected me:
> You're describing UTF-8.  UTF-16 uses 16-bit code units.>    
>  https://en.wikipedia.org/wiki/UTF-16


Jeez, yes, of course. Brainfart! Thanks.

--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: UTF16 to EBCDIC

[Phil Smith III]

Gil corrected me:

> You're describing UTF-8.  UTF-16 uses 16-bit code units.
>  
> https://en.wikipedia.org/wiki/UTF-16

 

Jeez, yes, of course. Brainfart! Thanks.


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

Re: Phases of Project in Mainframe

[Edward Finnell]

The latest SAPR I could find was for a Z10. Supposedly it all falls out with 
Workflow from OSMF but don't think you get the detail.

https://wiki.enterpriselab.ch/el/_media/mainframe:documentation:ibm_2097_z10_sapr_guide_tda_sa06-016-11.pdfIn
 a message dated 2/9/2020 9:21:28 PM Central Standard Time, idfli...@gmail.com 
writes:
for me , I need more information so i can see all the pieces
of a project, IMHO

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

Re: UTF16 to EBCDIC

[Paul Gilmartin]

On Sun, 9 Feb 2020 21:50:57 -0500, Phil Smith III wrote:

>Mike Schwab wrote:
>
>>Would UTF-16 to UTF-8 be a better conversion?  You still have to be
>>certain of the source character set.  And is supported by some z/OS
>>software.
>
I believe HLASM on Linux would probably mistake UTF-8 (IBM 1208)
SYSIN for ISO8859-1 and translate it SBCS-wise to IBM-037.  It might
even work if ISO code points 128-255 appear only in quoted strings.
E.g.   DC C'матрёшка'

COBOL?

>As Cameron indicated, your comment doesn't quite make sense. UTF-16 is just a 
>variable-length encoding, in which basic ASCII*
>(0-127) are single-byte, some characters are two-byte, some three-, and some 
>four-. More efficient, especially in the "mostly basic
>ASCII" case.
> 
You're describing UTF-8.  UTF-16 uses 16-bit code units.
https://en.wikipedia.org/wiki/UTF-16

-- gil

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

Re: UTF16 to EBCDIC

[Phil Smith III]

Mike Schwab wrote:

>Would UTF-16 to UTF-8 be a better conversion?  You still have to be

>certain of the source character set.  And is supported by some z/OS

>software.

 

As Cameron indicated, your comment doesn't quite make sense. UTF-16 is just a 
variable-length encoding, in which basic ASCII*
(0-127) are single-byte, some characters are two-byte, some three-, and some 
four-. More efficient, especially in the "mostly basic
ASCII" case.

 

*Yes, I know, talking about "ASCII" in the context of Unicode is dangerous and 
arguably incorrect. You know what I mean.


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

Re: UTF16 to EBCDIC

[Cameron Conacher]

Not sure what you are asking here.
The mainframe supports UTF-16BE Basic Mapping Plane 0 natively as National
Characters in COBOL - PIC N.

UTF-16 to UTF-8 would not lose any characters during transformation since
they both encode Unicode.


On Sun, Feb 9, 2020 at 6:21 PM Mike Schwab  wrote:

> Would UTF-16 to UTF-8 be a better conversion?  You still have to be
> certain of the source character set.  And is supported by some z/OS
> software.
>
> On Sun, Feb 9, 2020 at 11:55 AM Cameron Conacher 
> wrote:
> >
> > Ah yes,
> > I mis-typed/fat fingered the reply.
> > As you say, it SHOULD read EDCICONV.
> >
> > And, yes Unicode allows for over a million possible character
> combination.
> > National Language support in the mainframe allows for the characters in
> > basic mapping plane 0, so only about 65,000 character combinations.
> > And IBM-037 only has 256 combinations.
> > So, be aware of character loss as you transform from one to the other.
> >
> > On Sat, Feb 8, 2020 at 11:45 AM Paul Gilmartin <
> > 000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > > On Sat, 8 Feb 2020 09:09:58 -0600, Paul Gilmartin wrote:
> > >
> > > >On Sat, 8 Feb 2020 09:37:29 -0500, Cameron Conacher wrote:
> > > >
> > > >>I use ICONV.
> > > >>
> > > >>//MYSTEP EXEC PROC=EDICONV,
> > > >>//INFILE='MY.input.file.name(member)',
> > > >>//OUTFILE='My.Output.FileName',
> > > >>//FROMC='1208',
> > > >>//TOC='IBM-037'
> > > >>
> > > >>
> > > >>The PROC is licensed IBM material. It executes program EDICCONV
> > > >>
> > > >Is the documentation available only with purchase?
> > > >
> > > Ah!  Do you mean perhaps, JCL procedure EDCICONV?
> > >
> > >
> https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.cbcux01/iconvubatch.htm
> > >
> > > I wonder what was the motivation to require preallocated data set
> > > names rather than the more flexible alternative of DDNAMEs?
> > >
> > > >How does it handle characters absent from IBM-037?
> > > >
> > > >1208 is UTF-8, not UTF-16.  I assume the example is schematic.
> > >
> > > -- gil
> > >
> > > --
> > > 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
>
>
>
> --
> Mike A Schwab, Springfield IL USA
> Where do Forest Rangers go to get away from it all?
>
> --
> 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: UTF16 to EBCDIC

[Mike Schwab]

Would UTF-16 to UTF-8 be a better conversion?  You still have to be
certain of the source character set.  And is supported by some z/OS
software.

On Sun, Feb 9, 2020 at 11:55 AM Cameron Conacher  wrote:
>
> Ah yes,
> I mis-typed/fat fingered the reply.
> As you say, it SHOULD read EDCICONV.
>
> And, yes Unicode allows for over a million possible character combination.
> National Language support in the mainframe allows for the characters in
> basic mapping plane 0, so only about 65,000 character combinations.
> And IBM-037 only has 256 combinations.
> So, be aware of character loss as you transform from one to the other.
>
> On Sat, Feb 8, 2020 at 11:45 AM Paul Gilmartin <
> 000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>
> > On Sat, 8 Feb 2020 09:09:58 -0600, Paul Gilmartin wrote:
> >
> > >On Sat, 8 Feb 2020 09:37:29 -0500, Cameron Conacher wrote:
> > >
> > >>I use ICONV.
> > >>
> > >>//MYSTEP EXEC PROC=EDICONV,
> > >>//INFILE='MY.input.file.name(member)',
> > >>//OUTFILE='My.Output.FileName',
> > >>//FROMC='1208',
> > >>//TOC='IBM-037'
> > >>
> > >>
> > >>The PROC is licensed IBM material. It executes program EDICCONV
> > >>
> > >Is the documentation available only with purchase?
> > >
> > Ah!  Do you mean perhaps, JCL procedure EDCICONV?
> >
> > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.cbcux01/iconvubatch.htm
> >
> > I wonder what was the motivation to require preallocated data set
> > names rather than the more flexible alternative of DDNAMEs?
> >
> > >How does it handle characters absent from IBM-037?
> > >
> > >1208 is UTF-8, not UTF-16.  I assume the example is schematic.
> >
> > -- gil
> >
> > --
> > 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



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: UTF16 to EBCDIC

[Phil Smith III]

Gil wrote:

>But no indication that it throws an error.  Of course the iconv utility could 
>check
>the output of iconv() and report its own error.

 

Hmm. I thought I'd seen it throw an error but maybe not, and system is down ATM 
so I can't check

 

In any case, one approach might be to go UTF==>EBCDIC==>UTF and make sure it 
round-trips successfully, which it won't if it's lossy.

 

On my list of "things to do when I finish the time machine": No ASCII/EBCDIC 
divide; no null-terminated strings. And something else, I forget what right 
now. I have time, I can always do it last week.


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

Re: Caching Storage Control Ref Manuals

[William Donzelli]

> I’ve sort of become a computer storage historian for the Computer History 
> Museum and have a particular interest in the first IBM caching storage 
> controls, the 3880-11, 13, 21 and 23.  They were followed by the 3990.  IBM 
> distributed these manuals on CD-ROM usually called something like  Direct 
> Access Storage Subsystems Softcopy Library. I wonder if perhaps someplace in 
> someone's files there might be the CD-ROM or perhaps even paper reference 
> manuals for these storage controls?  If I can get a copy of either I can have 
> it posted to bitsavers or donate to the museum or both.

I am pretty sure I have fairly full sets of paper docs that came with
my 3880 and 3990. I do not know about the CDROM.

Like all the docs I have, Al has free reign on them if he wants to pay
shipping (and I am not sure when I am making another California trip).

This year I plan on actually organizing the library.

--
Will

--
Will

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

Re: Caching Storage Control Ref Manuals

[Susan Shumway]

Hi Tom,

I'll poke around here. If you don't hear back from me, I had no luck.

-Sue Shumway


On 2/9/2020 2:26 PM, Tom Gardner wrote:

I’ve sort of become a computer storage historian for the Computer History 
Museum and have a particular interest in the first IBM caching storage 
controls, the 3880-11, 13, 21 and 23.  They were followed by the 3990.  IBM 
distributed these manuals on CD-ROM usually called something like  Direct 
Access Storage Subsystems Softcopy Library. I wonder if perhaps someplace in 
someone's files there might be the CD-ROM or perhaps even paper reference 
manuals for these storage controls?  If I can get a copy of either I can have 
it posted to bitsavers or donate to the museum or both.

Thanks

Tom

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



--
Sue Shumway
z/OS Project Lead and Client Advocate
IBM Poughkeepsie
chale...@us.ibm.com

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

Re: Caching Storage Control Ref Manuals

[Seymour J Metz]

Don't forget the Airline Buffer.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of Tom 
Gardner 
Sent: Sunday, February 9, 2020 2:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Caching Storage Control Ref Manuals

I’ve sort of become a computer storage historian for the Computer History 
Museum and have a particular interest in the first IBM caching storage 
controls, the 3880-11, 13, 21 and 23.  They were followed by the 3990.  IBM 
distributed these manuals on CD-ROM usually called something like  Direct 
Access Storage Subsystems Softcopy Library. I wonder if perhaps someplace in 
someone's files there might be the CD-ROM or perhaps even paper reference 
manuals for these storage controls?  If I can get a copy of either I can have 
it posted to bitsavers or donate to the museum or both.

Thanks

Tom

--
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

Caching Storage Control Ref Manuals

[Tom Gardner]

I’ve sort of become a computer storage historian for the Computer History 
Museum and have a particular interest in the first IBM caching storage 
controls, the 3880-11, 13, 21 and 23.  They were followed by the 3990.  IBM 
distributed these manuals on CD-ROM usually called something like  Direct 
Access Storage Subsystems Softcopy Library. I wonder if perhaps someplace in 
someone's files there might be the CD-ROM or perhaps even paper reference 
manuals for these storage controls?  If I can get a copy of either I can have 
it posted to bitsavers or donate to the museum or both.

Thanks

Tom

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

Re: Phases of Project in Mainframe

[scott Ford]

Mike:

Highlevel to me is like a 'Management Summary'...Which is fine for managers
for me , I need more information so i can see all the pieces
of a project, IMHO

Scott

On Sun, Feb 9, 2020 at 10:19 AM Mike Smith  wrote:

> Peter,
>
> Parwez identified many of the physical steps necessary.  However, from
> your question I think you were hoping for a more high-level PM-ish kind of
> answer.
>
> From a very high level the project phases might include the following:
>
> Pre-Sales:
> The Presales Phase should include really understanding your environment
> and needs.  Performing a capacity study and modeling your workload on
> different capacities is only part of the effort.  You need to be educated
> on the new features and also any newer features from prior generations that
> might be of interest to you.  For example, today your enterprise may have a
> 10Gb network backbone in place, so you may want to eliminate any 1Gb OSAs
> (except for the ones used for consoles) and have your new system come in
> with the 10Gb OSAs.   Does you network team have plans to convert your 10Gb
> backbone to 25Gb in the next three to 5 years?  If so, then maybe 25Gb OSAs
> would be appropriate.
>
> Are you running any Linux on z (on IFLs) today?  If yes, the perhaps the
> Container Hosting Foundation feature should be ordered.  This is a
> relatively new feature that, along with support from z/OS 2.4, that allows
> you to run Linux containers under z/OS with the Linux workload running on
> zIIP engines, This is an intriguing idea especially for instances where
> there is fairly  tight integration/interaction between the z/OS and Linux
> portions of the workflow.  Just imagine, instead of having to set up a
> permanent Linux instance running somewhere, you can run it as a step in a
> batch job!
>
> What about your I/O configuration?  The z15 can be configured as a single
> frame CEC if you do not have a really large I/O configuration. Would this
> be appropriate for your environment?  This needs to be identified,
> discussed  and understood in the Presales phase to really determine if it
> is a viable configuration for your environment.
>
> Planning Phase:
> Next would come the planning phase.  this would be a collaborative effort
> between your team and the IBM or Business Partner team that is working with
> you on the project.   Much of the effort of the project will be in this
> phase.  Many of the things that Parwez identified and many more will be
> worked on and tracked to ensure that the cutover will be successful.
>
> Physical Installation:
> The Physical Installation is completed by IBM and the machine is cabled to
> your network, I/O devices, etc.
>
> Pre-Production Testing Phase:
> If it is possible that the current CEC and the new CEC can be up
> concurrently, this phase may take up to several weeks.  During this phase,
> test and/or sandbox LPARs may be brought up and tested, issues with ISV
> keys can be identified and corrected, etc.  This allows for through testing
> of the environment before cutting production over to the new CEC.
>
> However, if the production cutover needs to occur as close as possible to
> the physical install, then the Pre-Production testing phase is limited to
> much shorter time - maybe minutes or an hour or two.
>
> Production Cutover is the next phase.
> This is where the old CEC gets uncabled from the I/O and all effort
> transfers to getting the new CEC into production.
>
> Production Testing Phase
> The production testing phase immediately follows the production cutover.
> This phase may last up to several hours if your outage window and client
> commitments permit it.
>
> Milestone: Production testing  is followed by a Go/No Go decision
>
> Assuming that the decision is Go, you then proceed into the Post
> Implementation Phase.  However, if the decision is a No Go, then you
> proceed into the Fallback Phase.
>
> Fallback Phase.
> Take all steps necessary to swap the original CEC into production.  Then
> you will need to go back to the Planning or Pre-Production Testing phases.
>
> Post-Implementation Phase:
> Here you would monitor the environment for a few days with a heightened
> awareness and preform any clean-up from the cutover and pack up the old
> machine for return.
>
> This is obviously a very high level list and a lot of detail needs to be
> included.  The vendor team (either IBM or your IBM Business Partner)
> should  assist you with developing and implementing the plans.  The
> complexity and size of the planning effort varies for customer and each
> installation within that customers environment.
>
> I hope this helps.
>
> Regards,
> Mike Smith
>
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Parwez Hamid
> Sent: Monday, February 3, 2020 12:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Phases of Project in Mainframe
>
> This will differ for each customer and there will be a number of
> 

Re: Startio documentation

[David L. Craig]

On 20Feb09:0011+, Christopher Y. Blaicher wrote:

> Having done all of this, I would suggest that you start with EXCP and then 
> progress to EXPC/VR.  Even with EXCP you have to know and understand the 
> relationship of the CCW's you are going to use.  Read carefully.  Start 
> simple.  Build on it slowly.
> 
> Going from EXCP to EXCP/VR is a big jump.  Everything you have to do for 
> EXCP/VR you will have to do for STARTIO, plus more.
> 
> Once you have EXCP/VR running, go look at the STARTIO macro in SYS1.MODGEN.
> 
> EXCP and EXCP/VR have some guard rails built into them, but you can still 
> really screw things up at EXCP/VR because you will have to supply the REAL 
> addresses for the CCW's.
> 
> When, and if, you start playing with EXCP/VR, I strongly suggest using a 
> sandbox LPAR.  If you ever get to STARTIO that suggestion should rise to a 
> requirement.
> 
> Chris Blaicher
> Technical Architect
> Syncsort, Inc.

If z/VM is available, that's a godsend environment for safely seeing
what z/OS actually does in some of those nooks and crannies (definitely
if you're playing around with LPSW and the like).
-- 

May the LORD God bless you exceedingly abundantly!

Dave_Craig__
"So the universe is not quite as you thought it was.
 You'd better rearrange your beliefs, then.
 Because you certainly can't rearrange the universe."
__--from_Nightfall_by_Asimov/Silverberg_

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

Re: UTF16 to EBCDIC

[Cameron Conacher]

Ah yes,
I mis-typed/fat fingered the reply.
As you say, it SHOULD read EDCICONV.

And, yes Unicode allows for over a million possible character combination.
National Language support in the mainframe allows for the characters in
basic mapping plane 0, so only about 65,000 character combinations.
And IBM-037 only has 256 combinations.
So, be aware of character loss as you transform from one to the other.

On Sat, Feb 8, 2020 at 11:45 AM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On Sat, 8 Feb 2020 09:09:58 -0600, Paul Gilmartin wrote:
>
> >On Sat, 8 Feb 2020 09:37:29 -0500, Cameron Conacher wrote:
> >
> >>I use ICONV.
> >>
> >>//MYSTEP EXEC PROC=EDICONV,
> >>//INFILE='MY.input.file.name(member)',
> >>//OUTFILE='My.Output.FileName',
> >>//FROMC='1208',
> >>//TOC='IBM-037'
> >>
> >>
> >>The PROC is licensed IBM material. It executes program EDICCONV
> >>
> >Is the documentation available only with purchase?
> >
> Ah!  Do you mean perhaps, JCL procedure EDCICONV?
>
> https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.cbcux01/iconvubatch.htm
>
> I wonder what was the motivation to require preallocated data set
> names rather than the more flexible alternative of DDNAMEs?
>
> >How does it handle characters absent from IBM-037?
> >
> >1208 is UTF-8, not UTF-16.  I assume the example is schematic.
>
> -- gil
>
> --
> 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: Phases of Project in Mainframe

[Mike Smith]

Peter,

Parwez identified many of the physical steps necessary.  However, from your 
question I think you were hoping for a more high-level PM-ish kind of answer.

>From a very high level the project phases might include the following:

Pre-Sales:
The Presales Phase should include really understanding your environment and 
needs.  Performing a capacity study and modeling your workload on different 
capacities is only part of the effort.  You need to be educated on the new 
features and also any newer features from prior generations that might be of 
interest to you.  For example, today your enterprise may have a 10Gb network 
backbone in place, so you may want to eliminate any 1Gb OSAs (except for the 
ones used for consoles) and have your new system come in with the 10Gb OSAs.   
Does you network team have plans to convert your 10Gb backbone to 25Gb in the 
next three to 5 years?  If so, then maybe 25Gb OSAs would be appropriate.

Are you running any Linux on z (on IFLs) today?  If yes, the perhaps the 
Container Hosting Foundation feature should be ordered.  This is a relatively 
new feature that, along with support from z/OS 2.4, that allows you to run 
Linux containers under z/OS with the Linux workload running on  zIIP engines, 
This is an intriguing idea especially for instances where there is fairly  
tight integration/interaction between the z/OS and Linux portions of the 
workflow.  Just imagine, instead of having to set up a permanent Linux instance 
running somewhere, you can run it as a step in a batch job!

What about your I/O configuration?  The z15 can be configured as a single frame 
CEC if you do not have a really large I/O configuration. Would this be 
appropriate for your environment?  This needs to be identified, discussed  and 
understood in the Presales phase to really determine if it is a viable 
configuration for your environment.

Planning Phase:
Next would come the planning phase.  this would be a collaborative effort 
between your team and the IBM or Business Partner team that is working with you 
on the project.   Much of the effort of the project will be in this phase.  
Many of the things that Parwez identified and many more will be worked on and 
tracked to ensure that the cutover will be successful.

Physical Installation:
The Physical Installation is completed by IBM and the machine is cabled to your 
network, I/O devices, etc.

Pre-Production Testing Phase:
If it is possible that the current CEC and the new CEC can be up concurrently, 
this phase may take up to several weeks.  During this phase, test and/or 
sandbox LPARs may be brought up and tested, issues with ISV keys can be 
identified and corrected, etc.  This allows for through testing of the 
environment before cutting production over to the new CEC.

However, if the production cutover needs to occur as close as possible to the 
physical install, then the Pre-Production testing phase is limited to much 
shorter time - maybe minutes or an hour or two.

Production Cutover is the next phase.
This is where the old CEC gets uncabled from the I/O and all effort transfers 
to getting the new CEC into production.

Production Testing Phase
The production testing phase immediately follows the production cutover.  This 
phase may last up to several hours if your outage window and client commitments 
permit it.

Milestone: Production testing  is followed by a Go/No Go decision

Assuming that the decision is Go, you then proceed into the Post Implementation 
Phase.  However, if the decision is a No Go, then you proceed into the Fallback 
Phase.

Fallback Phase.
Take all steps necessary to swap the original CEC into production.  Then you 
will need to go back to the Planning or Pre-Production Testing phases.

Post-Implementation Phase:
Here you would monitor the environment for a few days with a heightened 
awareness and preform any clean-up from the cutover and pack up the old machine 
for return.

This is obviously a very high level list and a lot of detail needs to be 
included.  The vendor team (either IBM or your IBM Business Partner) should  
assist you with developing and implementing the plans.  The complexity and size 
of the planning effort varies for customer and each installation within that 
customers environment.

I hope this helps. 

Regards,
Mike Smith

 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Parwez Hamid
Sent: Monday, February 3, 2020 12:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Phases of Project in Mainframe

This will differ for each customer and there will be a number of dependencies. 
Key phases should cover (each topic will have its on subtasks):

1) Physical Planning (physical planning/power/space/channel cabling/network 
connectivity/HMCs etc etc)
2) Operating System levels etc
3) Capacity Planning. LPAR planning/configuration
4) ISV Software/products levels
5) Applications
6) DR/Backup
7) Operations procedures

I am sure 

Re: Startio documentation

[Christopher Y. Blaicher]

Here is an old manual that goes into detail about the CCW's for DASD.

http://dforeman.cs.binghamton.edu/~foreman/550pages/VM/z-Arch-DASD-CommandRef.pdf

Chris Blaicher
Technical Architect
Syncsort, Inc.


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mike Myers
Sent: Sunday, February 9, 2020 5:52 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Startio documentation

[ External - This message originated Externally.  Use proper judgment and 
caution with attachments, links, or responses. ]

Erik:

I took the reference I passed you earlier a bit further. If you look here, you 
will find a lot more detail on EXCP, EXCPVR and STARTIO. It's been a long time 
since I did my own channel programming and made use of EXCP, but I think you 
will find all you need to know here. You will also have to look into the 
structure of channel programming and CCWs for specific device types to 
understand more about what is really happening. 
The Principles of Operation can supply much of this.

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idas300/eyocp.htm

Mike Myers

On 2/8/20 10:26 PM, Susan Shumway wrote:
> Hi Erik,
>
> I searched the Technical help database for System z ( 
> https://www14.software.ibm.com/webapp/set2/psearch/search?domain=sysz
> ) and got plenty of hits for "startio", but none with the term in the 
> title. If you haven't looked there yet, give it a try and see if 
> anything looks helpful.
>
> There are also a number of hits to the term in the V2R4 KC, though 
> probably not true nerd brain entertainment fodder like what you're 
> looking for:
> https://www.ibm.com/support/knowledgecenter/search/startio?scope=SSLTB
> W_2.4.0 . Since it's just a simple term search, Mike's recommended KC 
> reading is most likely your better bet.
>
> -Sue Shumway
>
>
> On 2/8/2020 7:11 PM, Christopher Y. Blaicher wrote:
>> Having done all of this, I would suggest that you start with EXCP and 
>> then progress to EXPC/VR.  Even with EXCP you have to know and 
>> understand the relationship of the CCW's you are going to use.  Read 
>> carefully.  Start simple. Build on it slowly.
>>
>> Going from EXCP to EXCP/VR is a big jump.  Everything you have to do 
>> for EXCP/VR you will have to do for STARTIO, plus more.
>>
>> Once you have EXCP/VR running, go look at the STARTIO macro in 
>> SYS1.MODGEN.
>>
>> EXCP and EXCP/VR have some guard rails built into them, but you can 
>> still really screw things up at EXCP/VR because you will have to 
>> supply the REAL addresses for the CCW's.
>>
>> When, and if, you start playing with EXCP/VR, I strongly suggest 
>> using a sandbox LPAR.  If you ever get to STARTIO that suggestion 
>> should rise to a requirement.
>>
>> Chris Blaicher
>> Technical Architect
>> Syncsort, Inc.
>>
>>
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
>> On Behalf Of Mike Myers
>> Sent: Saturday, February 8, 2020 4:07 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: Startio documentation
>>
>> [ External - This message originated Externally.  Use proper judgment 
>> and caution with attachments, links, or responses. ]
>>
>> Hey Eric:
>>
>> You might want to start your exploration at a higher level than the 
>> lowest level you can possibly go to understand the internals of z/OS 
>> I/O. For example you might want to look at EXCP or EXCPVR first, as 
>> both prepare for entry into IOS, but both do special setup functions 
>> to make that possible.
>>
>> As an example of the setup needed, consider the difference between 
>> EXCP and EXCPVR. EXCP, among other preliminary things, converts all 
>> addresses in the channel program CCWs being passed to IOS from 
>> virtual to real addresses. Ultimately, these areas must be pagefixed 
>> so as to remain in storage during the actual I/O operation. Since 
>> STARTIO comes at the next lower level, everything that an access 
>> method must do before calling EXCP must also be done. This includes 
>> creating a DCB, an IOSB, etc.
>>
>> I would recommend you start here, if you haven't already. as it 
>> covers EXCP and EXCPVR.
>>
>> https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.
>> v2r1.idas300/eyocp.htm
>>
>>
>>
>> Mike Myers
>>
>> On 2/8/20 12:48 PM, Erik Janssen wrote:
>>> Hello List,
>>>
>>> Out of curiosity I want to learn a bit more about startio. Don't 
>>> worry, I won't go and attempt to mess up someones z/os lpar, it is 
>>> just for pure nerd brain entertainment. Searching through the 
>>> archives I found that there is a whitepaper that was written by 
>>> Peter Haas called "The STARTIO Facility of MVS", that there were 
>>> some examples called startio.txt or startio.ex.txt, that Bill 
>>> Fairchild gave a SHARE presentation on the subject in March 2009 in 
>>> Austin and that IBM documented it, partially, in IOS logic manuals; 
>>> the versions for
>>> OS/VS2 R2 through R3.8 were publicly 

Re: Startio documentation

[Binyamin Dissen]

STARTIO does not need no stinking DCB.

On Sat, 8 Feb 2020 16:06:56 -0500 Mike Myers  wrote:

:>Hey Eric:

:>You might want to start your exploration at a higher level than the 
:>lowest level you can possibly go to understand the internals of z/OS 
:>I/O. For example you might want to look at EXCP or EXCPVR first, as both 
:>prepare for entry into IOS, but both do special setup functions to make 
:>that possible.

:>As an example of the setup needed, consider the difference between EXCP 
:>and EXCPVR. EXCP, among other preliminary things, converts all addresses 
:>in the channel program CCWs being passed to IOS from virtual to real 
:>addresses. Ultimately, these areas must be pagefixed so as to remain in 
:>storage during the actual I/O operation. Since STARTIO comes at the next 
:>lower level, everything that an access method must do before calling 
:>EXCP must also be done. This includes creating a DCB, an IOSB, etc.

:>I would recommend you start here, if you haven't already. as it covers 
:>EXCP and EXCPVR.

:>https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idas300/eyocp.htm
 


:>Mike Myers

:>On 2/8/20 12:48 PM, Erik Janssen wrote:
:>> Hello List,

:>> Out of curiosity I want to learn a bit more about startio. Don't worry, I 
won't go and attempt to mess up someones z/os lpar, it is just for pure nerd 
brain entertainment. Searching through the archives I found that there is a 
whitepaper that was written by Peter Haas called "The STARTIO Facility of MVS", 
that there were some examples called startio.txt or startio.ex.txt, that Bill 
Fairchild gave a SHARE presentation on the subject in March 2009 in Austin and 
that IBM documented it, partially, in IOS logic manuals; the versions for
:>> OS/VS2 R2 through R3.8 were publicly available.

:>> My search engines efforts to find any of the mentioned documents have 
failed so far, so is there anybody on the list that has (some of) the mentioned 
documents available and is willing to share?

--
Binyamin Dissen 
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

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

Re: Startio documentation

[Mike Myers]

Erik:

I took the reference I passed you earlier a bit further. If you look 
here, you will find a lot more detail on EXCP, EXCPVR and STARTIO. It's 
been a long time since I did my own channel programming and made use of 
EXCP, but I think you will find all you need to know here. You will also 
have to look into the structure of channel programming and CCWs for 
specific device types to understand more about what is really happening. 
The Principles of Operation can supply much of this.


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idas300/eyocp.htm

Mike Myers

On 2/8/20 10:26 PM, Susan Shumway wrote:

Hi Erik,

I searched the Technical help database for System z ( 
https://www14.software.ibm.com/webapp/set2/psearch/search?domain=sysz 
) and got plenty of hits for "startio", but none with the term in the 
title. If you haven't looked there yet, give it a try and see if 
anything looks helpful.


There are also a number of hits to the term in the V2R4 KC, though 
probably not true nerd brain entertainment fodder like what you're 
looking for: 
https://www.ibm.com/support/knowledgecenter/search/startio?scope=SSLTBW_2.4.0 
. Since it's just a simple term search, Mike's recommended KC reading 
is most likely your better bet.


-Sue Shumway


On 2/8/2020 7:11 PM, Christopher Y. Blaicher wrote:
Having done all of this, I would suggest that you start with EXCP and 
then progress to EXPC/VR.  Even with EXCP you have to know and 
understand the relationship of the CCW's you are going to use.  Read 
carefully.  Start simple. Build on it slowly.


Going from EXCP to EXCP/VR is a big jump.  Everything you have to do 
for EXCP/VR you will have to do for STARTIO, plus more.


Once you have EXCP/VR running, go look at the STARTIO macro in 
SYS1.MODGEN.


EXCP and EXCP/VR have some guard rails built into them, but you can 
still really screw things up at EXCP/VR because you will have to 
supply the REAL addresses for the CCW's.


When, and if, you start playing with EXCP/VR, I strongly suggest 
using a sandbox LPAR.  If you ever get to STARTIO that suggestion 
should rise to a requirement.


Chris Blaicher
Technical Architect
Syncsort, Inc.


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
On Behalf Of Mike Myers

Sent: Saturday, February 8, 2020 4:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Startio documentation

[ External - This message originated Externally.  Use proper judgment 
and caution with attachments, links, or responses. ]


Hey Eric:

You might want to start your exploration at a higher level than the 
lowest level you can possibly go to understand the internals of z/OS 
I/O. For example you might want to look at EXCP or EXCPVR first, as 
both prepare for entry into IOS, but both do special setup functions 
to make that possible.


As an example of the setup needed, consider the difference between 
EXCP and EXCPVR. EXCP, among other preliminary things, converts all 
addresses in the channel program CCWs being passed to IOS from 
virtual to real addresses. Ultimately, these areas must be pagefixed 
so as to remain in storage during the actual I/O operation. Since 
STARTIO comes at the next lower level, everything that an access 
method must do before calling EXCP must also be done. This includes 
creating a DCB, an IOSB, etc.


I would recommend you start here, if you haven't already. as it 
covers EXCP and EXCPVR.


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idas300/eyocp.htm 




Mike Myers

On 2/8/20 12:48 PM, Erik Janssen wrote:

Hello List,

Out of curiosity I want to learn a bit more about startio. Don't
worry, I won't go and attempt to mess up someones z/os lpar, it is
just for pure nerd brain entertainment. Searching through the archives
I found that there is a whitepaper that was written by Peter Haas
called "The STARTIO Facility of MVS", that there were some examples
called startio.txt or startio.ex.txt, that Bill Fairchild gave a SHARE
presentation on the subject in March 2009 in Austin and that IBM
documented it, partially, in IOS logic manuals; the versions for
OS/VS2 R2 through R3.8 were publicly available.

My search engines efforts to find any of the mentioned documents 
have failed so far, so is there anybody on the list that has (some 
of) the mentioned documents available and is willing to share?


Kind regards,

Erik Janssen.
PS. I had posted the same question through Google groups, but that 
doesn't work in a way that the actual list gets the message it seems.


--
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