OPTCD=Q (was Conversion from Unisys Cobol file definitions to zOS)

[Terry Sambrooks]

Hi

In a recent post it was stated "Bottom line, I think it's pretty clearly
documented that BSAM/QSAM supports character set conversion, but only when
tape is involved. I agree that that's a pretty ridiculous restriction" and
this was for both OPRCD=Q and CCSID. 

This may seem like a ridiculous restriction but I see no incentive or
requirement to change it. OPTCD=Q in particular harks back to when most
installations transferred data via tape, not even cartridge in those days.
Here in the UK all the main banks used IBM equipment but the central
clearing centre for Standing Orders and Direct Debits used an indigenous
system and hence OPTCD=Q was used a lot.

These days most organisations rely on network transfers and have bespoke
products such as Connect Direct to handle the traffic. These products are
more than capable of handling character conversion as a minimum. 

Looking back at the original post it seem that the issue was more
sophisticated than simple character conversion and related to field
alignment and sizes, i.e. converting a 3-digit field with a length of one
and half bytes into a two byte field.

Kind Regards - Terry
 
Director
KMS-IT Limited
228 Abbeydale Road South
Dore
Sheffield
S17 3LA
UK
 
Reg : 3767263
 
Outgoing e-mails have been scanned, but it is the recipients responsibility
to ensure their anti-virus software is up to date.
 
 


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

Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT

[willie bunter]

Lizette,

Thanks for the info.  For this dsn in particular there is no migration it is to 
be expired/deleted after 1 day of non-usage.

You have touched on the point of space management algorithms for migration.  I 
assume that this would also pertain to the deletion of files as well. Right?


On Thu, 1/14/16, Lizette Koehler  wrote:

 Subject: Re: DFHSM/SMS QUESTION -  SPACE MANAGEMENT
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, January 14, 2016, 12:45 PM
 
 So depending on the
 version of z/OS - look at On Demand Migration (v2.1 and
 above), this might help more
 
 Second, correct, files are only moved if DFHSM
 feels the volume needs to have the space back, however, you
 could  have a migration policy in the management class that
 says - if this is still on DASD after 1 month, then migrate
 the file.
 
 It depends on
 what your requirements are.  You can just let files migrate
 as HSM sees fit based on its algorithms for space
 management, or you can setup a management class that says it
 gets migrated if unused in XX days.
 
 Many choices.
 
 Lizette
 
 >
 -Original Message-
 > From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of willie bunter
 > Sent: Thursday, January 14, 2016 10:23
 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: DFHSM/SMS QUESTION - SPACE
 MANAGEMENT
 > 
 > Good
 Day To All,
 > 
 > I
 need to confirm if I my understanding about SMS & SPACE
 management is
 > correct.
 > We have noticed that there are several
 dsns which have been on dasd for over
 >
 10 months.  The volumes and dsns are all SMS managed and
 DFHSM performs the
 > necessary migration
 and deletion.  I checked the MANAGEMENT class and the
 dsns
 > are to be deleted after 1 day
 non-usage
 > 
 > Expire
 after Days Non-usage  . : 1
 > Expire
 after Date/Days . . . .      : 1
 >
 Retention Limit  . . . . . . .           :
 0
 > 
 > Below are the
 attributes of the Storage Group:
 > 
 > 
 > Allocation/migration
 Threshold :            High   
 85   (1-100)  Low . . 1
 >
 (0-99)
 > Alloc/Migr Threshold
 Track-Managed:  High    85   (1-100)    Low
 . . 1   (0-
 > 99)
 > Guaranteed Backup Frequency  . . . . .
 .                  (1 to  or
 > NOLIMIT)
 >
 BreakPointValue  . . . . . . . . . . . .           
                  (0-65520
 > or blank)
 > Processing
 Priority  . . . . . . . . . . 50   
    (1-100)
 > 
 > I think that the dsns are not deleted
 because SMS did not select some of these
 > volumes have not met the criteria of the
 Low threshold of 1.  I remember
 >
 reading somewhere (on this board the following):
 > 
 > For primary space
 management, HSM only looks at the low threshold. If the
 > volume exceeds the low threshold, then we
 will process any data sets that are
 >
 eligible for migration on that volume.
 >
 
 > Could someone confirm if I am
 correct?
 > 
 >
 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

DFHSM/SMS QUESTION - SPACE MANAGEMENT

[willie bunter]

Good Day To All,

I need to confirm if I my understanding about SMS & SPACE management is correct.
We have noticed that there are several dsns which have been on dasd for over 10 
months.  The volumes and dsns are all SMS managed and DFHSM performs the 
necessary migration and deletion.  I checked the MANAGEMENT class and the dsns 
are to be deleted after 1 day non-usage

Expire after Days Non-usage  . : 1
Expire after Date/Days . . . .  : 1
Retention Limit  . . . . . . .   : 0

Below are the attributes of the Storage Group:


Allocation/migration Threshold :High85   (1-100)  Low . . 1   
(0-99) 
Alloc/Migr Threshold Track-Managed:  High85   (1-100)Low . . 1   (0-99) 
Guaranteed Backup Frequency  . . . . . .  (1 to  or 
NOLIMIT)  
BreakPointValue  . . . . . . . . . . . . (0-65520 
or blank)  
Processing Priority  . . . . . . . . . . 50   (1-100) 

I think that the dsns are not deleted because SMS did not select some of these 
volumes have not met the criteria of the Low threshold of 1.  I remember 
reading somewhere (on this board the following):

For primary space management, HSM only looks at the low threshold. If the 
volume exceeds the low threshold, then we will process any data sets that are 
eligible for migration on that volume. 

Could someone confirm if I am correct?

Thanks.

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

Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT

[Lizette Koehler]

So depending on the version of z/OS - look at On Demand Migration (v2.1 and 
above), this might help more

Second, correct, files are only moved if DFHSM feels the volume needs to have 
the space back, however, you could  have a migration policy in the management 
class that says - if this is still on DASD after 1 month, then migrate the file.

It depends on what your requirements are.  You can just let files migrate as 
HSM sees fit based on its algorithms for space management, or you can setup a 
management class that says it gets migrated if unused in XX days.

Many choices.

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of willie bunter
> Sent: Thursday, January 14, 2016 10:23 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: DFHSM/SMS QUESTION - SPACE MANAGEMENT
> 
> Good Day To All,
> 
> I need to confirm if I my understanding about SMS & SPACE management is
> correct.
> We have noticed that there are several dsns which have been on dasd for over
> 10 months.  The volumes and dsns are all SMS managed and DFHSM performs the
> necessary migration and deletion.  I checked the MANAGEMENT class and the dsns
> are to be deleted after 1 day non-usage
> 
> Expire after Days Non-usage  . : 1
> Expire after Date/Days . . . .  : 1
> Retention Limit  . . . . . . .   : 0
> 
> Below are the attributes of the Storage Group:
> 
> 
> Allocation/migration Threshold :High85   (1-100)  Low . . 1
> (0-99)
> Alloc/Migr Threshold Track-Managed:  High85   (1-100)Low . . 1   (0-
> 99)
> Guaranteed Backup Frequency  . . . . . .  (1 to  or
> NOLIMIT)
> BreakPointValue  . . . . . . . . . . . . (0-65520
> or blank)
> Processing Priority  . . . . . . . . . . 50   (1-100)
> 
> I think that the dsns are not deleted because SMS did not select some of these
> volumes have not met the criteria of the Low threshold of 1.  I remember
> reading somewhere (on this board the following):
> 
> For primary space management, HSM only looks at the low threshold. If the
> volume exceeds the low threshold, then we will process any data sets that are
> eligible for migration on that volume.
> 
> Could someone confirm if I am correct?
> 
> Thanks.

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

Re: Why doesn't "="option work in SMP/E panels?

[Elardus Engelbrecht]

Vernooij, CP (ITOPT1) - KLM wrote:

>That is the only technically correct answer. For that reason I have macro 
>button in my terminal emulator that does: =x;=x;=x;=x;=x;=x;=x;=x; to get back 
>home from wherever you are. 

About SMP/E Primary Option Menu which is coded with " = YES", it is 
indeed the correct answer. 

PF2 + PF9 to split and swap is also a good alternative method.

As others also said, ISMF and IPCS also do that.

Because of that, I have added several 'shortcut commands' in option =3.9 
'application command table'. There you can go to another application on top of 
SMP/E, ISMF, SDSF, Bookmanager, RACF, whatever. 

Then you go recursively back to your previous application. For example, someone 
in a storage group sees a message in SDSF, he then goes to ISMF (that's the 
command ISMF!), works on ISMF, then exit ISMF back to SDSF. After that he can 
works on SDSF.

Of course, that eats memory, but memory is cheap-cheap! ;-)

>Further, we have a lot of handy commands to go directly to useful functions. 
>From any panel I can enter: DSL to invoke the DSLIST panel directly. 
 
Also using =3.9 in TSO?

Groete / Greetings
Elardus Engelbrecht

"I get no respect from my wife, I once fell asleep with a cigarette in my hand. 
She lit it." (Rodney Dangerfield)

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

Re: Why doesn't "="option work in SMP/E panels?

[Richards, Robert B.]

I wholeheartedly concur with Elardus on the specification and usage of command 
table entries (3.9).

I use SITE table 1 in 3.9 and currently have 137 entries in it. The majority of 
entries are invoked using two characters. When done, PF3 returns you to the 
location where you invoked the command table entry. I rarely type a "= JUMP" 
command. You want SMPE, type SMP or SMPE, you want RACF, type RAC or RACF. 
SYSLOG? Type SL.  Operlog?  Type OL. ISRDDN? Type DDN.

I also use  where appropriate and have added SCRNAME to most entries. 
Very useful when using SWAPBAR.

Most commonly used by me?  SMPE, DDN, SDH (SDSF H),  SDD (SDSF DA), ISH 
(ISHELL), UL (ULOG) and the previously mentioned SL and OL

I also have entries to invoke most ISV product dialogs, but I won't specify any 
of them here. :-)

Bob


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Thursday, January 14, 2016 3:15 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why doesn't "="option work in SMP/E panels?

Vernooij, CP (ITOPT1) - KLM wrote:

>That is the only technically correct answer. For that reason I have macro 
>button in my terminal emulator that does: =x;=x;=x;=x;=x;=x;=x;=x; to get back 
>home from wherever you are. 

About SMP/E Primary Option Menu which is coded with " = YES", it is 
indeed the correct answer. 

PF2 + PF9 to split and swap is also a good alternative method.

As others also said, ISMF and IPCS also do that.

Because of that, I have added several 'shortcut commands' in option =3.9 
'application command table'. There you can go to another application on top of 
SMP/E, ISMF, SDSF, Bookmanager, RACF, whatever. 

Then you go recursively back to your previous application. For example, someone 
in a storage group sees a message in SDSF, he then goes to ISMF (that's the 
command ISMF!), works on ISMF, then exit ISMF back to SDSF. After that he can 
works on SDSF.

Of course, that eats memory, but memory is cheap-cheap! ;-)

>Further, we have a lot of handy commands to go directly to useful functions. 
>From any panel I can enter: DSL to invoke the DSLIST panel directly. 
 
Also using =3.9 in TSO?

Groete / Greetings
Elardus Engelbrecht

"I get no respect from my wife, I once fell asleep with a cigarette in my hand. 
She lit it." (Rodney Dangerfield)

--
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: Conversion from Unisys Cobol file definitions to zOS

[Pew, Curtis G]

> On Jan 13, 2016, at 10:56 PM, Paul Gilmartin 
> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> 
> But does mere mention of OPTCD=Q mean its use is restricted to tapes?
> Might not it apply to other device types?  (It's hard to prove a negative)
> But if it's so restricted it's another instance of IBM's implementing a
> useful facility at the wrong layer.  ASCII<->EBCDIC conversion is surely
> useful on other device types.

The JCL Reference manual says for OPTCD=Q:

indicates that all the user data in the data set is in ASCII. BSAM or QSAM 
converts the records from ASCII to EBCDIC when reading and converts the records 
from EBCDIC to ASCII when writing. The data set must reside on magnetic tape 
and must not contain IBM standard labels. The record format (RECFM) must not be 
V but can be D. If the label type is ISO/ANSI/FIPS, specified as LABEL=(,AL), 
the system forces OPTCD=Q.

> 
> Is this software in the OS or microcode in the control unit?

I’m pretty sure it’s in the BSAM/QSAM access method routines.

> 
> And what about CCSID.  According to the documentation, this:

In the JCL manual under CCSID, it says:

Data conversion is supported on access to ISO/ANSI Version 4 tapes using access 
methods BSAM or QSAM, but not using EXCP.


Bottom line, I think it’s pretty clearly documented that BSAM/QSAM supports 
character set conversion, but only when tape is involved. I agree that that’s a 
pretty ridiculous restriction.

-- 
Pew, Curtis G
curtis@austin.utexas.edu
ITS Systems/Core/Administrative Services


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

Re: BCPii setup questions

[Skip Robinson]

Radislow,

Your subsequent posts suggest that you have solved at least some of your
problems. Could you please restate which if any are still troublesome?

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of R.S.
> Sent: Wednesday, January 13, 2016 09:23 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [Bulk] BCPii setup questions
> 
> I'm trying to setup BCPii.
> I did some RTFM, but still have questions.
> 
> What I achieved is communication with SE:
> HWI007I BCPII IS ATTEMPTING COMMUNICATION WITH THE LOCAL CENTRAL
> PROCESSOR COMPLEX (CPC).
> HWI001I BCPII IS ACTIVE.
> 
> However I have problems with security.
> 
> 1. How to assign userid to HWIBCPII address space? Regular profile
> (HWIBCPII.*) in STARTED class doesn't work.
> Note: I'm asking about HWIBCPII, not HWISTART.
> 
> 2. I was trying to use some HCD facilities requiring BCPii, got "8 0F02"
> (not enough authority) but no ICH408I occured in syslog. Is it normal?
> 
> 3. What authorities should have HWIBCPII user?
> As far as I understand BCPii user must be authorized to various HWI.nnn
> profiles in FACILITY class, but no clue about BCPii address space
reqirements.
> 
> Other questions:
> 4. What can I do with IBM products/features using BCPii?
> I'm aware of Parallel Sysplex (SSDPP), CPM and HCD.
> For HCD I found only the option 2.11.V (Build and manage S/390
> microprocessor IOCDSs and IPL attributes - Work with CPC images), which is
> not very useful.
> 
> 5. I only used BCPii on local CPC.
> Can I use BCPii to query/manage other machine?
> How?
> Is it enough to define HWI.TARGET.IBM390PS.P0012345 profile with proper
> SNMP string? What about LPAR security?
> 
> 
> Regards
> --
> Radoslaw Skorupka
> Lodz, Poland

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

Re: JES2 to JES3 Migration

[Lizette Koehler]

Cheryl,

I am guessing you meant the subject to say JES3 to JES2 migration???

The one challenge I see is the JCL is different between the two environments.  
JES2 use /* (eg. /*ROUTE) and JES3 uses //* (eg //*MAIN)   

JES2 has no master JES system, JES3 has a Master.  So in JES2 jobs can either 
run where the JCL is converted or anywhere in the JESMAS.


There is also the concept in JES3 that until all resources available, the job 
will not run.  JES2 it can run and wind up waiting on resources.

Those are about the differences I can think of off the top of my head.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Cheryl Watson
> Sent: Thursday, January 14, 2016 7:01 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: JES2 to JES3 Migration
> 
> A customer asked us for suggestions for performing a JES3 to JES2 migration.
> Are there products that will help in this, or do you know any companies who
> perform this migration?  You can reply off-list if you prefer.
> 
> Thanks so much,
> Cheryl
> cheryl at watsonwalker.com

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

JES2 to JES3 Migration

[Cheryl Watson]

A customer asked us for suggestions for performing a JES3 to JES2 migration.  
Are there products that will help in this, or do you know any companies who 
perform this migration?  You can reply off-list if you prefer.

Thanks so much,
Cheryl
cheryl at watsonwalker.com

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

Re: JES3 to JES2 Migration (was JES2 to JES3 Migration)

[Cheryl Watson]

Yes, Lizette - I meant to say JES3 to JES2.  Thanks!

Has anyone who has done this have an estimate of the amount of time it might 
take, and the effort?

Cheryl

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Thursday, January 14, 2016 9:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 to JES3 Migration

Cheryl,

I am guessing you meant the subject to say JES3 to JES2 migration???

The one challenge I see is the JCL is different between the two environments.  
JES2 use /* (eg. /*ROUTE) and JES3 uses //* (eg //*MAIN)   

JES2 has no master JES system, JES3 has a Master.  So in JES2 jobs can either 
run where the JCL is converted or anywhere in the JESMAS.


There is also the concept in JES3 that until all resources available, the job 
will not run.  JES2 it can run and wind up waiting on resources.

Those are about the differences I can think of off the top of my head.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Cheryl Watson
> Sent: Thursday, January 14, 2016 7:01 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: JES2 to JES3 Migration
> 
> A customer asked us for suggestions for performing a JES3 to JES2 migration.
> Are there products that will help in this, or do you know any 
> companies who perform this migration?  You can reply off-list if you prefer.
> 
> Thanks so much,
> Cheryl
> cheryl at watsonwalker.com

--
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: BCPii setup questions

[R.S.]

Yes, I "solved" problem #1. It was my mistake (plus some error in 
documentation). Regular STARTED profile do work as it should. Another 
level of complexity was added here by the method of starting HWIBCPII.


Regarding 2 and 3 - documentation is not clear for me and the lack of 
ICH408I does not allow to distinguish lack of authorities from other 
problems.


Regarding #4 - no clue. I learned REXX support is for z/OS 2.x (I'm on 
1.13).


Regarding #5 - I managed the connectivity to other CPC (after fixing 
some ugly typo). Despite some Share presentations it obviously requires 
LAN connectivity, but not between z/OS images, rather between "source" 
CPC's Support Element and "target" CPC's SE.
(clarification: source - a CPC when BCPII address space is running. 
target - object managed by BCPii)
As I wrote above, I did it, but I would like to know guidelines or 
recommendations.


Regards
--
Radoslaw Skorupka
Lodz, Poland






W dniu 2016-01-14 o 17:54, Skip Robinson pisze:

Radislow,

Your subsequent posts suggest that you have solved at least some of your
problems. Could you please restate which if any are still troublesome?

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of R.S.
Sent: Wednesday, January 13, 2016 09:23 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [Bulk] BCPii setup questions

I'm trying to setup BCPii.
I did some RTFM, but still have questions.

What I achieved is communication with SE:
HWI007I BCPII IS ATTEMPTING COMMUNICATION WITH THE LOCAL CENTRAL
PROCESSOR COMPLEX (CPC).
HWI001I BCPII IS ACTIVE.

However I have problems with security.

1. How to assign userid to HWIBCPII address space? Regular profile
(HWIBCPII.*) in STARTED class doesn't work.
Note: I'm asking about HWIBCPII, not HWISTART.

2. I was trying to use some HCD facilities requiring BCPii, got "8 0F02"
(not enough authority) but no ICH408I occured in syslog. Is it normal?

3. What authorities should have HWIBCPII user?
As far as I understand BCPii user must be authorized to various HWI.nnn
profiles in FACILITY class, but no clue about BCPii address space

reqirements.

Other questions:
4. What can I do with IBM products/features using BCPii?
I'm aware of Parallel Sysplex (SSDPP), CPM and HCD.
For HCD I found only the option 2.11.V (Build and manage S/390
microprocessor IOCDSs and IPL attributes - Work with CPC images), which is
not very useful.

5. I only used BCPii on local CPC.
Can I use BCPii to query/manage other machine?
How?
Is it enough to define HWI.TARGET.IBM390PS.P0012345 profile with proper
SNMP string? What about LPAR security?


Regards
--
Radoslaw Skorupka
Lodz, Poland

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





--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru 
Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci 
wpacony) wynosi 168.955.696 zotych.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to 

Re: z/OS 2.1 and FONTS; Moving from z/OS 1.13

[Gibney, David Allen,Jr]

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Elardus Engelbrecht
> Sent: Wednesday, January 13, 2016 9:40 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: z/OS 2.1 and FONTS; Moving from z/OS 1.13
> 
> Gibney, David Allen,Jr wrote:
> 
> >   I have a small shop, 4 monoplex LPARs, no GRS. Very careful sharing of a
> limited set of disks including the system resident (IPL) volume, a Mod-27. Up
> until now, I have made separate (R/O) copies of the ROOT and other system
> ZFS/HFS(s) for each LPARs.
> >   This new Unix filesystem with FONTS is not small and I am wondering if it
> is  safe to have only one (R/O) copy of it (probably on the IPL volume), 
> shared
> by two or more LPARs?
> 
> That's possible (sharing of IPL volser) as long all those LPARS are on the 
> same
> z/OS level.

I have been sharing the traditional RESVOL since at least z/OS 1.7

> 
> >   My SMP/E points to an entirely separate target Mod 27 and set of OMVS
> files. These are cloned after maintenance to alternating IPL and maintenance
> level OMVS files.
> 
> What is your catalog setup? Do you have separate master catalogs and their
> own set of user catalogs? Or are you sharing your catalogs?
> 

Mostly LPAR specific catalog systems. My two sandboxes share several USERCATS.
OMVS HLQ is in the unshared Master(s)  Which could complicate things :) 


> I believe it is safe to share a Read Only OMVS dataset, unless you have
> something to prevent sharing of such OMVS datasets, for example having a
> folder which is written to.

I am figuring on mounting them R/O. 

> 
> Of course, moving from z/OS v1.13 to 2.1 requires two different IPL volsers
> during rolling upgrades.

All independent monoplexes, but yes new IPL volumes for the new 2.1 system. No 
real co-existence, just need to insure viable fallback. Never been able to 
justify the CPU resources for even basic Sysplex. And never really had the 
need. We have multiple Lpars to isolate production from development from 
sandbox work.

Part of my concern is that I only have 16 M27 defined. (user to make do with 12 
M9 before our last DASD upgrade). I'm running short until I complete the 
migrations

> 
> Groete / Greetings
> Elardus Engelbrecht
> 
> --
> 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: Conversion from Unisys Cobol file definitions to zOS

[Robert A. Rosenberg]

At 09:26 -0600 on 01/13/2016, Paul Gilmartin wrote about Re: 
Conversion from Unisys Cobol file definitions to zOS:



Does OPTCD=Q work on all device types?  I had got the impression it
applied only to tapes.


My impression may be wrong but I seem to remember that OPTCD=Q was 
used ONLY on 7-track tapes. This might be that the non-IBM machines 
writing ASCII only wrote 7-Track Tapes and did not support 8-Track 
tapes. This was years ago when I needed to support it and things 
probably have changed since then.


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

Re: Server retired after 18 years and ten months - beat that, readers!

[retired mainframer]

Haven't there been stories quoted here about government agencies (Social
Security, DMV, VA) using 20 and 30 year old equipment?

My shop used an MP2003(-103?) for over 15 years.  It was connected to three
3174s that had also been used by its father and grandfather for at least the
first 20 years I worked there.  (One 3174 failed to power up after one of
the Christmas shutdowns sometime after year 15.  We kept it for spare parts
if ever needed.)  I'm pretty sure the 800/1600 BPI round reel tape drives we
used were much older than my grandchildren and not much younger than my
children.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Ed Gould
> Sent: Thursday, January 14, 2016 9:01 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: OT: Server retired after 18 years and ten months - beat that,
readers!
> 
> http://www.theregister.co.uk/2016/01/14/
> server_retired_after_18_years_and_ten_months_beat_that_readers/
> 
> 
> Server retired after 18 years and ten months - beat that, readers!
> 
> Home-brew 200Mhz Pentium FreeBSD box ran custom code that made
> replacement painful
> --
> 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: Server retired after 18 years and ten months - beat that, readers!

[Ed Finnell]

Voyager still truckin' along. Launched in 1977.
 
https://en.wikipedia.org/wiki/Voyager_program#Computers
 
 
 
In a message dated 1/14/2016 11:33:22 P.M. Central Standard Time,  
retired-mainfra...@q.com writes:

Haven't  there been stories quoted here about government agencies (Social
Security,  DMV, VA) using 20 and 30 year old  equipment?



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

Re: Conversion from Unisys Cobol file definitions to zOS

[Paul Gilmartin]

On Fri, 15 Jan 2016 00:28:41 -0500, Robert A. Rosenberg wrote:
>
>... did not support 8-Track tapes.  ...
> 
Weren't those mostly used in automobiles?  I remember when a colleague
first saw a 3480 cartridge he asked, "Is that an 8-track?"

-- gil

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

Re: JES3 to JES2 Migration (was JES2 to JES3 Migration)

[Klaus Stanislawiak]

Cheryl.

You may want to take a look at the IBM® Redbook® "JES3 to JES2 Migration 
Considerations":
http://publib-b.boulder.ibm.com/abstracts/sg248083.html?Open

And new functions (Job Execution Controls) have been introduced with z/OS 2.2 
JES2.
They are not yet mentioned in the Redbook, but may provide additional help with 
the migration.

Klaus

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

OT: Server retired after 18 years and ten months – beat that, readers!

[Ed Gould]

http://www.theregister.co.uk/2016/01/14/ 
server_retired_after_18_years_and_ten_months_beat_that_readers/



Server retired after 18 years and ten months – beat that, readers!

Home-brew 200Mhz Pentium FreeBSD box ran custom code that made  
replacement painful

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

Re: Conversion from Unisys Cobol file definitions to zOS

[Timothy Sipples]

Curtis Pew wrote:
>Bottom line, I think it’s pretty clearly documented that BSAM/QSAM
>supports character set conversion, but only when tape is involved.

Or virtual tape.


Timothy Sipples
IT Architect Executive, Industry Solutions, IBM z Systems, AP/GCG/MEA


E-Mail: sipp...@sg.ibm.com

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

Re: Server retired after 18 years and ten months - beat that, readers!

[William Donzelli]

> Haven't there been stories quoted here about government agencies (Social
> Security, DMV, VA) using 20 and 30 year old equipment?

Machines that have run for 20 or 30 years are not as rare as one might
think. There are still a few CDC machines in real service today, for
example - and when did the last Cyber roll off the factory floor?
There is even an early 1960s built CDC minicomputer in the middle of
nowhere running a radar station. My own IBM 4331 ran for nearly 30
years, and it *never* had a service call. However, the owner of the
tiny company that had it tuned it off every weekend to save power, so
not 25/7/365.

--
Will.

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

Re: Conversion from Unisys Cobol file definitions to zOS

[Ed Finnell]

It's been years but I got involved in Notis(library) imports that were  
Ascii 8trks. The first cut was OTPCD=Q, but it was a 'strict ASCII' that didn't 
 convert diacriticals. Think they ended up using SAS but it's been a very  
long time.
 
 
In a message dated 1/14/2016 11:29:26 P.M. Central Standard Time,  
hal9...@panix.com writes:

used  ONLY on 7-track tapes. This might be that the non-IBM machines 
writing  ASCII only wrote 7-Track Tapes and did not support 8-Track 
tapes. This was  years ago when I needed to support it and things 
probably have changed  since then.


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

Re: Conversion from Unisys Cobol file definitions to zOS

[Ed Finnell]

VHS or Beta Max. 9trks for 3420's.
 
 
In a message dated 1/15/2016 12:20:59 A.M. Central Standard Time,  
000433f07816-dmarc-requ...@listserv.ua.edu writes:

Weren't  those mostly used in automobiles?  I remember when a colleague
first  saw a 3480 cartridge he asked, "Is that an  8-track?"



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

Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT

[Gibney, David Allen,Jr]

Also, what are the actual dataset attributes? DFHSM doesn't do some 
"incomplete" datasets. Are they backed up. DFHSM often doesn't delete if there 
is not a back-up.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of willie bunter
> Sent: Thursday, January 14, 2016 9:53 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT
> 
> Lizette,
> 
> Thanks for the info.  For this dsn in particular there is no migration it is 
> to be
> expired/deleted after 1 day of non-usage.
> 
> You have touched on the point of space management algorithms for
> migration.  I assume that this would also pertain to the deletion of files as
> well. Right?
> 
> 
> On Thu, 1/14/16, Lizette Koehler  wrote:
> 
>  Subject: Re: DFHSM/SMS QUESTION -  SPACE MANAGEMENT
>  To: IBM-MAIN@LISTSERV.UA.EDU
>  Received: Thursday, January 14, 2016, 12:45 PM
> 
>  So depending on the
>  version of z/OS - look at On Demand Migration (v2.1 and  above), this might
> help more
> 
>  Second, correct, files are only moved if DFHSM  feels the volume needs to
> have the space back, however, you  could  have a migration policy in the
> management class that  says - if this is still on DASD after 1 month, then
> migrate  the file.
> 
>  It depends on
>  what your requirements are.  You can just let files migrate  as HSM sees fit
> based on its algorithms for space  management, or you can setup a
> management class that says it  gets migrated if unused in XX days.
> 
>  Many choices.
> 
>  Lizette
> 
>  >
>  -Original Message-
>  > From: IBM
>  Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]  On  >
> Behalf Of willie bunter  > Sent: Thursday, January 14, 2016 10:23  AM  > To:
> IBM-MAIN@LISTSERV.UA.EDU  > Subject: DFHSM/SMS QUESTION - SPACE
> MANAGEMENT  >  > Good  Day To All,  >  > I  need to confirm if I my
> understanding about SMS & SPACE  management is  > correct.
>  > We have noticed that there are several  dsns which have been on dasd for
> over  >
>  10 months.  The volumes and dsns are all SMS managed and  DFHSM
> performs the  > necessary migration  and deletion.  I checked the
> MANAGEMENT class and the  dsns  > are to be deleted after 1 day  non-usage
> >  > Expire  after Days Non-usage  . : 1  > Expire  after Date/Days . . . .   
> >    : 1
> >  Retention Limit  . . . . . . .           :
>  0
>  >
>  > Below are the
>  attributes of the Storage Group:
>  >
>  >
>  > Allocation/migration
>  Threshold :            High
>  85   (1-100)  Low . . 1
>  >
>  (0-99)
>  > Alloc/Migr Threshold
>  Track-Managed:  High    85   (1-100)    Low  . . 1   (0-  > 99)  > Guaranteed
> Backup Frequency  . . . . .
>  .                  (1 to  or
>  > NOLIMIT)
>  >
>  BreakPointValue  . . . . . . . . . . . .
>                   (0-65520
>  > or blank)
>  > Processing
>  Priority  . . . . . . . . . . 50
>     (1-100)
>  >
>  > I think that the dsns are not deleted  because SMS did not select some of
> these  > volumes have not met the criteria of the  Low threshold of 1.  I
> remember  >  reading somewhere (on this board the following):
>  >
>  > For primary space
>  management, HSM only looks at the low threshold. If the  > volume exceeds
> the low threshold, then we  will process any data sets that are  >  eligible 
> for
> migration on that volume.
>  >
> 
>  > Could someone confirm if I am
>  correct?
>  >
>  >
>  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: DFHSM/SMS QUESTION - SPACE MANAGEMENT

[Lizette Koehler]

What does your management class for this dataset say as well as the HSM policy?

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of willie bunter
> Sent: Thursday, January 14, 2016 10:53 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT
> 
> Lizette,
> 
> Thanks for the info.  For this dsn in particular there is no migration it is
> to be expired/deleted after 1 day of non-usage.
> 
> You have touched on the point of space management algorithms for migration.  I
> assume that this would also pertain to the deletion of files as well. Right?
> 
> 
> On Thu, 1/14/16, Lizette Koehler  wrote:
> 
>  Subject: Re: DFHSM/SMS QUESTION -  SPACE MANAGEMENT
>  To: IBM-MAIN@LISTSERV.UA.EDU
>  Received: Thursday, January 14, 2016, 12:45 PM
> 
>  So depending on the
>  version of z/OS - look at On Demand Migration (v2.1 and  above), this might
> help more
> 
>  Second, correct, files are only moved if DFHSM  feels the volume needs to
> have the space back, however, you  could  have a migration policy in the
> management class that  says - if this is still on DASD after 1 month, then
> migrate  the file.
> 
>  It depends on
>  what your requirements are.  You can just let files migrate  as HSM sees fit
> based on its algorithms for space  management, or you can setup a management
> class that says it  gets migrated if unused in XX days.
> 
>  Many choices.
> 
>  Lizette
> 
>  >
>  -Original Message-
>  > From: IBM
>  Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]  On  > Behalf Of
> willie bunter  > Sent: Thursday, January 14, 2016 10:23  AM  > To: IBM-
> m...@listserv.ua.edu  > Subject: DFHSM/SMS QUESTION - SPACE  MANAGEMENT  >  >
> Good  Day To All,  >  > I  need to confirm if I my understanding about SMS &
> SPACE  management is  > correct.
>  > We have noticed that there are several  dsns which have been on dasd for
> over  >
>  10 months.  The volumes and dsns are all SMS managed and  DFHSM performs the
> > necessary migration  and deletion.  I checked the MANAGEMENT class and the
> dsns  > are to be deleted after 1 day  non-usage  >  > Expire  after Days Non-
> usage  . : 1  > Expire  after Date/Days . . . .  : 1  >  Retention
> Limit  . . . . . . .   :
>  0
>  >
>  > Below are the
>  attributes of the Storage Group:
>  >
>  >
>  > Allocation/migration
>  Threshold :High
>  85   (1-100)  Low . . 1
>  >
>  (0-99)
>  > Alloc/Migr Threshold
>  Track-Managed:  High85   (1-100)Low  . . 1   (0-  > 99)  > Guaranteed
> Backup Frequency  . . . . .
>  .  (1 to  or
>  > NOLIMIT)
>  >
>  BreakPointValue  . . . . . . . . . . . .
>   (0-65520
>  > or blank)
>  > Processing
>  Priority  . . . . . . . . . . 50
> (1-100)
>  >
>  > I think that the dsns are not deleted  because SMS did not select some of
> these  > volumes have not met the criteria of the  Low threshold of 1.  I
> remember  >  reading somewhere (on this board the following):
>  >
>  > For primary space
>  management, HSM only looks at the low threshold. If the  > volume exceeds the
> low threshold, then we  will process any data sets that are  >  eligible for
> migration on that volume.
>  >
> 
>  > Could someone confirm if I am
>  correct?
>  >
>  >
>  Thanks.

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