date:20170206

On Tue, 7 Feb 2017 07:04:38 +0200, Binyamin Dissen wrote:

>I wrote my own QPAM.
> 
According to hearsay, so have others.  This is evidence of a need which should
have resulted in an RFE.  If one was ever submitted, I wonder what became of it?

-- gil

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

AW: Re: DB2 Locks and WLM Blocked Workload Support?

2017-02-06 Thread Peter Hunkeler

Excellent! Exactly the information I was looking for. Thank you, Horst and Greg.


--
Peter Hunkeler






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

AW: Re: DB2 Locks and WLM Blocked Workload Support?

2017-02-06 Thread Peter Hunkeler


>If you have not done so, you might also want to post to the DB2 List who may 
>have more experience.


First line of my post gives you the answer ;-)

>>Cross-posted from DB2-L



--
Peter Hunkeler



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

Re: BSAM vs QSAM

I wrote my own QPAM.

On Mon, 6 Feb 2017 20:07:23 -0500 Steve Smith  wrote:

:>I've often wondered why there is no QPAM.  It seems to me that it should
:>hardly involve more than a bit of glue code to swap some fields around here
:>and there.
:>
:>sas
:>
:>On Mon, Feb 6, 2017 at 12:24 PM, Binyamin Dissen > wrote:
:>
:>> Also, reading a PDS member by member requires BPAM (which is really BSAM).
:>>
:>>

--
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: BSAM vs QSAM (and SORT).

2017-02-06 Thread Joel C. Ewing

Back in the days of uncompressed tape blocks (reel-to-reel, & early
3480) there was a nice one-to-one correspondence between a fixed point
on the tape within a block and all the bits in a byte in parallel tracks
on the tape, so it was actually relatively simple to pass the tape past
the heads in the reverse direction and read all the bytes within a block
in reverse order and all the blocks in reverse order at full read speed
with the tape continually moving in reverse.  Tape sorts made use of
that to eliminate the repeated several-minute rewind time each time
another pass over the tape data was required.

I never had to deal with  reverse-read I/O, but PofOp indicates that one
supplied the address of the high end of the buffer as the channel
program data address and the channel decremented rather than incremented
byte addresses while transferring bytes to memory, so that the bytes of
a block would be restored to correct order in memory but would be
high-justified rather than low-justified in the buffer for short blocks.
 So the channel hardware itself effectively reversed the order of bytes
as they were read in reverse order.

I believe once the physical tape blocks became compressed (3480C and
later) it became impossible to actually read the physical blocks with
the tape moving in reverse and extract the original bytes on the fly.
Read reverse on such drives would no doubt have been emulated by the
device by backspacing over blocks, reading physical blocks with a
forward read, extracting the bytes, figuring out what bytes to supply to
the channel in reverse order to be consistent with what read-reverse
should have produced, then backspacing again to get to preceding block
and repeating.  Reversing the tape direction repeatedly while reading an
entire tape in reverse would  totally kill performance on one of those
drives.

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

zOS SYSPROG jobs

2017-02-06 Thread Steve Beaver

I am getting at least one call a day (zOS SYSPROG/ARCHITECT jobs) that want
me to relocate to somewhere I don't care to be and they refuse to allow
remote at least 75% of the time then they do not want to pay all my
expenses.  

The latest rash is for the DC/BWI area are that need people with SECRET or
better clearances -- That is no problem and they will get close to what I am
asking, but I have had enough of traveling and living in hotels for their
convenience not mine.

Steve  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Clark Morris
Sent: Monday, February 6, 2017 8:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mainframe jobs

[Default] On 6 Feb 2017 11:53:05 -0800, in bit.listserv.ibm-main
li...@akphs.com (Phil Smith III) wrote:

>Network World:
>
>By some estimates there will be more than 84,000 open positions in this 
>field by 2020.
>
> 
>
>http://www.networkworld.com/article/3161857/hardware/as-baby-boomers-re
>tire- the-shortage-of-mainframe-professionals-grows-more-acute.html
>
Given the slow and steady attrition of z series shops and movement to the
cloud, I do not believe it.  Are the salaries for mainframe technical people
increasing?  Are there mass recruitments for COBOL programmers or increased
salaries and contract rates?  I am grateful to have been able to retire when
I did.  I doubt the estimates given on the number of lines of COBOL source
for programs that are still actively in production given the number of
systems that have been replaced by packages such as SAP.  What is the
attendance at SHARE these days?  I doubt it is as high as when I was
participating in it.
Guide has been gone since 1999.  I doubt many of the newer ISV packages are
written in COBOL.  There isn't the same small system support for the 360
architecture there used to be and I doubt many organizations upgrade to z
from the IBM i series.  If any organization starts out on any system that is
ASCII/ISO oriented, I don't see that organization going through the pain to
get to z/OS and conversion to EBCDIC.  

Unisys is selling Intel based servers running either OS2200 or MCP, with at
least the OS2200 based systems running with emulated code through firmware.
I doubt either are being sold to new customers.

Given the various Windows, Linux and Unix offerings I doubt there is much of
a growth market for z series or for any other mainframe architecture. 

Incidentally, how secure is TPF?  I understand that it used be sort of like
Windows 3.1 in that everything was in the same address space for
performance.

If your shop was on Windows or some Unix variant for all of its processing,
would you recommend converting to z series?

Clark Morris 
> 
>
>Now, that would be nice, but.um.I don't think so.
>
>
>--
>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: Mainframe jobs

2017-02-06 Thread Jack J. Woehr


Clark Morris wrote:

  Are there mass recruitments for COBOL
programmers or increased salaries and contract rates?


There are shops that can't escape z and their staff are all retiring as you did and those shops are now at the mercy of 
external IT support offerings who are hiring system programmers.


--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan

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

Re: Mainframe jobs

2017-02-06 Thread Clark Morris

[Default] On 6 Feb 2017 11:53:05 -0800, in bit.listserv.ibm-main
li...@akphs.com (Phil Smith III) wrote:

>Network World:
>
>By some estimates there will be more than 84,000 open positions in this
>field by 2020.
>
> 
>
>http://www.networkworld.com/article/3161857/hardware/as-baby-boomers-retire-
>the-shortage-of-mainframe-professionals-grows-more-acute.html 
>
Given the slow and steady attrition of z series shops and movement to
the cloud, I do not believe it.  Are the salaries for mainframe
technical people increasing?  Are there mass recruitments for COBOL
programmers or increased salaries and contract rates?  I am grateful
to have been able to retire when I did.  I doubt the estimates given
on the number of lines of COBOL source for programs that are still
actively in production given the number of systems that have been
replaced by packages such as SAP.  What is the attendance at SHARE
these days?  I doubt it is as high as when I was participating in it.
Guide has been gone since 1999.  I doubt many of the newer ISV
packages are written in COBOL.  There isn't the same small system
support for the 360 architecture there used to be and I doubt many
organizations upgrade to z from the IBM i series.  If any organization
starts out on any system that is ASCII/ISO oriented, I don't see that
organization going through the pain to get to z/OS and conversion to
EBCDIC.  

Unisys is selling Intel based servers running either OS2200 or MCP,
with at least the OS2200 based systems running with emulated code
through firmware.  I doubt either are being sold to new customers.

Given the various Windows, Linux and Unix offerings I doubt there is
much of a growth market for z series or for any other mainframe
architecture. 

Incidentally, how secure is TPF?  I understand that it used be sort of
like Windows 3.1 in that everything was in the same address space for
performance.

If your shop was on Windows or some Unix variant for all of its
processing, would you recommend converting to z series?

Clark Morris 
> 
>
>Now, that would be nice, but.um.I don't think so.
>
>
>--
>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: Eight-character TSO Userid Support

2017-02-06 Thread Tom Conley


On 2/6/2017 7:37 PM, Paul Gilmartin wrote:

On 2017-02-06, at 12:51, Jesse 1 Robinson wrote:


In one sense, TSO userids have always 'tied up' 8 bytes, but the first byte by 
convention has always been the length of the actual userid in the next 7 
characters. This structure is utterly pervasive throughout TSO(/E). Not just 
IBM processes but countless RYO and third party processes as well. Even the 
structure of UADS for a user is set of multiple members named as userid+digit, 
which requires an id of 7 characters or less.


UADS has outlived its usefulness.


The motivation for the increased length seems to me entirely a matter of 
responding (dare I say catering?) to grousing from the non-mainframe world 
where in many shops, the TSO id has to be different from the all other 
applications that allow a full 8 characters. I don't find that requirement 
offensive because in many shops, TSO ids are assigned by a pattern representing 
department affiliation, where the first few characters indicate the users' 
function. This actually simplifies access rules, since all, say, STORxxx users 
can be granted elevated DASD management authority. If the person changes 
function, you want the userid to lose the old authority in favor of whatever 
comes next.


I categorize it as "Plays well with others."  (Not!)  One more impediment
for the sales force to overcome.


I've never been a promoter of increased userid length because I don't think 
it's worth the enormous trouble it will cause. I think the vast majority of 
shops will refrain from pulling the 8-character trigger and live comfortable 
with the world as it's always been.


Dismayingly ironically, the need has been addressed by UNIX System Services:
• z/OS 2.2.0
• z/OS UNIX System Services
• z/OS UNIX System Services Planning
• Customizing z/OS UNIX
• Customizing the BPXPRMxx member of SYS1.PARMLIB
• Defining system features
• USERIDALIASTABLE
This augments the character vocabulary of login IDs by mapping them
onto classic user IDs.  But:
o It retains for aliases the 8-character limit prevalent for user
  IDs elsewhere in z/OS.  (Only TSO has the 7-character limit.)
  It would have been an excellent opportunity to go to longer IDs
  such as the 32 which I understand Linux supports.
o It applies only to UNIX logons, not to ID management in general.
  Compatibility obstacles are nicely overcome because UNIX syscalls
  deal in the aliases, classic facilities in the classic IDs.
o Most dismayingly, it uses a collateral (UNIX) file with attendant
  performance impact, described as varying directly with the number
  of IDs aliased.  This should have properly been implemented
  uniformly in the RACF DB.

Conway's Law again, dammit!  A solution is devised but its applicability
is restricted because of deficient communication among development
groups.

-- gil


I must say one thing.  This entire post by Gil is untrue.  His 
conjecture about we should have done 32 characters would have made this 
project wait at least another, and possibly two releases of z/OS.  The 
line about deficient communication is unadulterated bull@#$%.  A large 
number of people at both IBM and OEM vendors have been working for years 
to deliver 8-character TSO support.  The work these people have done is 
worthy of praise, not damnation.  A non-disclosure prevents me from 
saying more at this time, but for the folks on the list, you need to 
know that Gil is completely wrong on this issue.


Regards,
Tom Conley

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

Re: BSAM vs QSAM

On Mon, 6 Feb 2017 20:07:23 -0500, Steve Smith wrote:

>I've often wondered why there is no QPAM.  It seems to me that it should
>hardly involve more than a bit of glue code to swap some fields around here
>and there.
> 
I could imagie QNOTE and QPOINT, dealing with a 6-byte token:
TTRZ + 16-bit offset within block.

-- gil

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

Re: BSAM vs QSAM

2017-02-06 Thread Steve Smith

I've often wondered why there is no QPAM.  It seems to me that it should
hardly involve more than a bit of glue code to swap some fields around here
and there.

sas

On Mon, Feb 6, 2017 at 12:24 PM, Binyamin Dissen  wrote:

> Also, reading a PDS member by member requires BPAM (which is really BSAM).
>
>
-- 
sas

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

Re: Eight-character TSO Userid Support

On 2017-02-06, at 12:51, Jesse 1 Robinson wrote:

> In one sense, TSO userids have always 'tied up' 8 bytes, but the first byte 
> by convention has always been the length of the actual userid in the next 7 
> characters. This structure is utterly pervasive throughout TSO(/E). Not just 
> IBM processes but countless RYO and third party processes as well. Even the 
> structure of UADS for a user is set of multiple members named as 
> userid+digit, which requires an id of 7 characters or less.  
>  
UADS has outlived its usefulness.

> The motivation for the increased length seems to me entirely a matter of 
> responding (dare I say catering?) to grousing from the non-mainframe world 
> where in many shops, the TSO id has to be different from the all other 
> applications that allow a full 8 characters. I don't find that requirement 
> offensive because in many shops, TSO ids are assigned by a pattern 
> representing department affiliation, where the first few characters indicate 
> the users' function. This actually simplifies access rules, since all, say, 
> STORxxx users can be granted elevated DASD management authority. If the 
> person changes function, you want the userid to lose the old authority in 
> favor of whatever comes next.  
>  
I categorize it as "Plays well with others."  (Not!)  One more impediment
for the sales force to overcome.

> I've never been a promoter of increased userid length because I don't think 
> it's worth the enormous trouble it will cause. I think the vast majority of 
> shops will refrain from pulling the 8-character trigger and live comfortable 
> with the world as it's always been.  
>  
Dismayingly ironically, the need has been addressed by UNIX System Services:
• z/OS 2.2.0
• z/OS UNIX System Services
• z/OS UNIX System Services Planning
• Customizing z/OS UNIX
• Customizing the BPXPRMxx member of SYS1.PARMLIB
• Defining system features
• USERIDALIASTABLE
This augments the character vocabulary of login IDs by mapping them
onto classic user IDs.  But:
o It retains for aliases the 8-character limit prevalent for user
  IDs elsewhere in z/OS.  (Only TSO has the 7-character limit.)
  It would have been an excellent opportunity to go to longer IDs
  such as the 32 which I understand Linux supports.
o It applies only to UNIX logons, not to ID management in general.
  Compatibility obstacles are nicely overcome because UNIX syscalls
  deal in the aliases, classic facilities in the classic IDs.
o Most dismayingly, it uses a collateral (UNIX) file with attendant
  performance impact, described as varying directly with the number
  of IDs aliased.  This should have properly been implemented
  uniformly in the RACF DB.

Conway's Law again, dammit!  A solution is devised but its applicability
is restricted because of deficient communication among development
groups.

-- gil

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

Re: H1B minimum wage increase.

2017-02-06 Thread Neil Duffee

Actually, $130k is a reporting exemption minimum.

"... raises the salary level at which H1B dependent employer are 

exempt from non-displacement and recruitment attestation requirements 

to greater than $130,000."

However, I expect the intention *is* to reduce H1Bs without changing actual 
quotas. (by raising the burden of proof.)

>  signature = 8 lines follows  <
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585  fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
“How *do* you plan for something like that?”  Guardian Bob, Reboot
“For every action, there is an equal and opposite criticism.”
“Systems Programming: Guilty, until proven innocent”  John Norgauer 2004
"Schrodinger's backup: The condition of any backup is unknown until a restore 
is attempted."  John McKown 2015


-Original Message-
From: Mike Schwab [mailto:mik...a...sc...@gma...com] 
Sent: February 2, 2017 05:09
Subject: H1B minimum wage increase.

http://www.business-standard.com/article/companies/blow-for-indian-it-new-us-bill-proposes-doubling-wage-limit-for-h1b-visa-117013100477_1.html

$130,000 minimum wage for H1B technology workers?  Might be worth paying 
american workers $80,000.

--
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: SCDS/ACDS Compare Tool

2017-02-06 Thread Neil Duffee

Not a 'tool' exactly but I wrote a similar *raw* comparison job to do what 
you're seeking.  It uses IDCAMS DCOLLECT SMSDATA() where SCDSNAME(ACTIVE) gives 
you the equivalent values that are found in the current ACDS.  You then SuperC 
that vs. the SCDSNAME() you're looking to activate/validate.  

Unfortunately, there will always be deltas [1] if only for internal dates;  so 
I wrote myself a SAS program that does a raw comparison, ignoring the record 
header stuffs, and provides offsets & lengths that can be used with the 
DCOLLECT records layouts in the AMS appendix.  That illustrated to me that the 
information in 'Reserved' fields will *not* be equal.  Still, it, along with an 
IDCAMS PRINT of both, made the manual investigation simpler and could be used 
as backup documentation when printed/annotated/filed.

I'll bundle up the 10 member library for those that want.  (I never considered 
it for CBT since it's *really* just an augmented SuperC.)

[1]  I just re-ran the job comparing the activating SCDS against the ACTIVE and 
SuperC gives 980 deltas.  The SAS program 'wheedles' that down to 367 items to 
check. (only 16 of those are non-SG related.)

>  signature = 8 lines follows  <
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585  fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
"How *do* you plan for something like that?"  Guardian Bob, Reboot
"For every action, there is an equal and opposite criticism."
"Systems Programming: Guilty, until proven innocent"  John Norgauer 2004
"Schrodinger's backup: The condition of any backup is unknown until a restore 
is attempted."  John McKown 2015

-Original Message-
From: retired mainframer [mailto:ret..-ma...@q...com] 
Sent: February 3, 2017 00:03
Subject: Re: SCDS/ACDS Compare Tool

You could use ISMF to print the various classes and ACS routines, one dataset 
with the "current" output and the other with the SCDS output.  Then SUPERC the 
two listings and let management think they understand what the differences mean.

> -Original Message-
> From: IBM Mainframe Discussion List 
> On Behalf Of Chuck Kreiter
> Sent: Thursday, February 02, 2017 10:19 AM
> Subject: SCDS/ACDS Compare Tool
> 
> Management at my company wants to see a delta compare of the ACDS and 
> the "to be activated" SCDS so that they can see what is going to be 
> implemented
> with a given change.  I've asked IBM and they were not aware of anything.
> I've looked at Naviquest and it can do some but not everything.  A 
> FileManger compare of the files doesn't produce anything useful.  
> Anyone know of such a tool or process to produce such a compare?

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

Re: Eight-character TSO Userid Support

2017-02-06 Thread Jesse 1 Robinson

I stand edified. Had not seen the inverse, which I feel is kind of unusual. In 
general, when a field is governed by a length indicator, it seems that most 
often the length comes first. In this case, since the overall field itself is 
fixed, it doesn't much matter where you put the length. Maybe an EXecute MVC or 
CLC is a tad simpler if the thing being handled comes first. In any case, 
finding room for an 8th meaningful character is going to be a massive 
undertaking. Besides OA51203 (which looks like Omegamon), there are going to be 
a ton of supporting APARs.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of David Cole
Sent: Monday, February 06, 2017 12:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Eight-character TSO Userid Support

At 2/6/2017 02:51 PM, Jesse 1 Robinson wrote:
"In one sense, TSO userids have always 'tied up' 8 bytes, but the first byte by 
convention has always been the length of the actual userid in the next 7 
characters. This structure is utterly pervasive throughout TSO(/E). Not just 
IBM processes but countless RYO and third party processes as well. Even the 
structure of UADS for a user is set of multiple members named as userid+digit, 
which requires an id of 7 characters or less."

Uh no. In a couple of major TSO cblocks, it's a 7 character field FOLLOWED by 
the length field...

Examples:

PSCBUSER DSCL7  USERID PADDED RIGHT WITH 
BLANKS 03-IKJPSCB
PSCBUSRL DSCL1  LENGTH OF 
USERID03-IKJPSCB

and

UPTPREFX DSCL7  DSNAME 
PREFIXY02669 03-IKJUPT
UPTPREFL DSBL1  LENGTH OF DSNAME 
PREFIX  Y02669 03-IKJUPT

Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS:dbc...@colesoft.com

Home page:   www.colesoft.com
LinkedIn:www.xdc.com
Facebook:www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware


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

Re: Eight-character TSO Userid Support

2017-02-06 Thread David Cole


At 2/6/2017 02:51 PM, Jesse 1 Robinson wrote:
"In one sense, TSO userids have always 'tied up' 8 bytes, but the 
first byte by convention has always been the length of the actual 
userid in the next 7 characters. This structure is utterly pervasive 
throughout TSO(/E). Not just IBM processes but countless RYO and 
third party processes as well. Even the structure of UADS for a user 
is set of multiple members named as userid+digit, which requires an 
id of 7 characters or less."


Uh no. In a couple of major TSO cblocks, it's a 7 character field 
FOLLOWED by the length field...


Examples:

PSCBUSER DSCL7  USERID PADDED RIGHT WITH 
BLANKS 03-IKJPSCB
PSCBUSRL DSCL1  LENGTH OF 
USERID03-IKJPSCB


and

UPTPREFX DSCL7  DSNAME 
PREFIXY02669 03-IKJUPT
UPTPREFL DSBL1  LENGTH OF DSNAME 
PREFIX  Y02669 03-IKJUPT


Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS:dbc...@colesoft.com

Home page:   www.colesoft.com
LinkedIn:www.xdc.com
Facebook:www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware

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

Re: BSAM vs QSAM (and SORT).

2017-02-06 Thread Blaicher, Christopher Y.

If you consider me one of the SORT experts, I have been involved with sort 
development since the early 80's, and never once ran a tape sort.

When I first worked for Liberty Mutual Insurance, we had a 7074 hypervisor 
running on a 360/65 and I saw a tape sort running there, but never wrote any 
code for it or the Syncsort version.

Chris Blaicher
Technical Architect
Mainframe Development
Syncsort Incorporated
2 Blue Hill Plaza #1563, Pearl River, NY 10965

P: 201-930-8234  |  M: 512-627-3803
E: cblaic...@syncsort.com

www.syncsort.com

CONNECTING BIG IRON TO BIG DATA

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Monday, February 6, 2017 1:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: BSAM vs QSAM (and SORT).

On 2017-02-06, at 07:22, R.S. wrote:
>
> It's worth to mention that performance of reverse processing dataset on real 
> tape is worse than horrible.
> And IMHO it's not argument for using virtual tapes but for not using datasets 
> on tape for applications. Tapes are for backup and ML2.
>
I had understood that old-fashioned SORT with SORTWK on tape employed read 
backwards very effectively.  Perhaps the SORT expert will jump in:
https://en.wikipedia.org/wiki/Oscillating_merge_sort

It was spectacular to watch.  Are the data un-reversed by hardware, firmware, 
or software?

On 2017-02-06, at 10:24, Binyamin Dissen wrote:

> Also, reading a PDS member by member requires BPAM (which is really BSAM).
>
Which was our motivation, when I was in a small group supporting a FOSS 
compiler and runtime library, for implementing BPAM and BSAM but not QSAM.  
Once we had the BPAM interface, most of the interface could likewise be used 
for BSAM.

Ironically, not burdened by the extreme storage constraints of OS/360, our 
compiler eschewed most of BPAM.  At a COPY-type operation we simply opened 
another DCB, processed the member to the end, then popped back to the parent 
member; no NOTE or POINT involved.  Worked great on MVS; not at all on CMS "OS 
Emulation".

-- gil

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

ATTENTION: -

The information contained in this message (including any files transmitted with 
this message) may contain proprietary, trade secret or other confidential 
and/or legally privileged information. Any pricing information contained in 
this message or in any files transmitted with this message is always 
confidential and cannot be shared with any third parties without prior written 
approval from Syncsort. This message is intended to be read only by the 
individual or entity to whom it is addressed or by their designee. If the 
reader of this message is not the intended recipient, you are on notice that 
any use, disclosure, copying or distribution of this message, in any form, is 
strictly prohibited. If you have received this message in error, please 
immediately notify the sender and/or Syncsort and destroy all copies of this 
message in your possession, custody or control.

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

OPEN INPUT file-name REVERSED was Re: BSAM vs QSAM

2017-02-06 Thread Clark Morris

[Default] On 6 Feb 2017 11:46:22 -0800, in bit.listserv.ibm-main
t...@harminc.net (Tony Harminc) wrote:

>On 6 February 2017 at 09:22, R.S.  wrote:
>
>> W dniu 2017-02-06 o 14:59, Ron Burr pisze:
>>
>>> As far as I know, reading a physical sequential (or partitioned dataset
>>> member) in reverse order can only be done using BSAM (via the BSP macro).
>>> Not that many applications require that mode of processing. But if one
>>> does, well then, that appears to be the only option. Mind you, there are
>>> some restrictions inherent in using BSP, as the manual explains.
>>> The COBOL manual states that you can process a QSAM tape dataset in
>>> reverse order by doing an OPEN REVERSED, but I suspect that the dataset
>>> will actually be processed using BSAM, not QSAM.
>>>
>>
>> It's worth to mention that performance of reverse processing dataset on
>> real tape is worse than horrible.
>> And IMHO it's not argument for using virtual tapes but for not using
>> datasets on tape for applications. Tapes are for backup and ML2.
>>
>
>Are you two perhaps mixing reading in "reverse order" of records with "read
>backward"? Read Backward is a CCW that (on old reel-to-reel tapes, at
>least) moves the tape backwards past the read head and transfers data into
>main storage in byte-by-byte decreasing address order. So the data ends up
>in normal order in storage, but if your app knows somehow that the tape is
>positioned at the end of the data, it doesn't have to rewind or backspace
>and then read forward.
>
>I have no idea if any modern real or virtual tape supports this, or if
>COBOL or even BSAM/QSAM ever did.

IBM 360/370/390/Enterprise COBOLs implement both CLOSE NO REWIND and
OPEN INPUT REVERSED for single reel files.  The read reversed was a
function used by tape sorts where the work files were on tape.

AIX COBOLs accept and ignore the REVERSED and NO REWIND statements.

Clark Morris
>
>Tony H.
>
>--
>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

Mainframe jobs

2017-02-06 Thread Phil Smith III

Network World:

By some estimates there will be more than 84,000 open positions in this
field by 2020.

 

http://www.networkworld.com/article/3161857/hardware/as-baby-boomers-retire-
the-shortage-of-mainframe-professionals-grows-more-acute.html 

 

Now, that would be nice, but.um.I don't think so.


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

Re: Eight-character TSO Userid Support

2017-02-06 Thread Jesse 1 Robinson

In one sense, TSO userids have always 'tied up' 8 bytes, but the first byte by 
convention has always been the length of the actual userid in the next 7 
characters. This structure is utterly pervasive throughout TSO(/E). Not just 
IBM processes but countless RYO and third party processes as well. Even the 
structure of UADS for a user is set of multiple members named as userid+digit, 
which requires an id of 7 characters or less.  

The motivation for the increased length seems to me entirely a matter of 
responding (dare I say catering?) to grousing from the non-mainframe world 
where in many shops, the TSO id has to be different from the all other 
applications that allow a full 8 characters. I don't find that requirement 
offensive because in many shops, TSO ids are assigned by a pattern representing 
department affiliation, where the first few characters indicate the users' 
function. This actually simplifies access rules, since all, say, STORxxx users 
can be granted elevated DASD management authority. If the person changes 
function, you want the userid to lose the old authority in favor of whatever 
comes next.  

I've never been a promoter of increased userid length because I don't think 
it's worth the enormous trouble it will cause. I think the vast majority of 
shops will refrain from pulling the 8-character trigger and live comfortable 
with the world as it's always been.  

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Monday, February 06, 2017 11:12 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Eight-character TSO Userid Support

On 2017-02-06, at 08:29, John McKown wrote:

> On Mon, Feb 6, 2017 at 8:45 AM, Edward Gould 
> wrote:
>> 
>> Thanks, I wonder how much  IBM and user code is going to have to 
>> change to allow this?
>>  
I suppose it depends on whether your installation exploits the feature.

DSN prefix?  SUBMIT?  OUTPUT?  (I'd prefer to see SUBMIT modified to relax the 
F80 limit.)

> Very true. I know of a lot of control block which look something like:
> 
> USERID   DS 0CL8
> USERIDL  DS FL1
> USERIDV  DS CL7
>  
Why in that order rather than the reverse?

All in all, it's underreaching to break compatibility for a 15% increase.  
While 8 is a pervasive enterprise convention, many OSes (Linux? OS X? (I just 
succeeded with 32)) allow far more.  Better to allow a long login name to map 
to a short UID.

-- gil

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

Re: BSAM vs QSAM

2017-02-06 Thread Tony Harminc

On 6 February 2017 at 09:22, R.S.  wrote:

> W dniu 2017-02-06 o 14:59, Ron Burr pisze:
>
>> As far as I know, reading a physical sequential (or partitioned dataset
>> member) in reverse order can only be done using BSAM (via the BSP macro).
>> Not that many applications require that mode of processing. But if one
>> does, well then, that appears to be the only option. Mind you, there are
>> some restrictions inherent in using BSP, as the manual explains.
>> The COBOL manual states that you can process a QSAM tape dataset in
>> reverse order by doing an OPEN REVERSED, but I suspect that the dataset
>> will actually be processed using BSAM, not QSAM.
>>
>
> It's worth to mention that performance of reverse processing dataset on
> real tape is worse than horrible.
> And IMHO it's not argument for using virtual tapes but for not using
> datasets on tape for applications. Tapes are for backup and ML2.
>

Are you two perhaps mixing reading in "reverse order" of records with "read
backward"? Read Backward is a CCW that (on old reel-to-reel tapes, at
least) moves the tape backwards past the read head and transfers data into
main storage in byte-by-byte decreasing address order. So the data ends up
in normal order in storage, but if your app knows somehow that the tape is
positioned at the end of the data, it doesn't have to rewind or backspace
and then read forward.

I have no idea if any modern real or virtual tape supports this, or if
COBOL or even BSAM/QSAM ever did.

Tony H.

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

Re: DB2 Locks and WLM Blocked Workload Support?

2017-02-06 Thread Horst Sinram

Peter,

DB2 has the most comprehensive support to interact with WLM to address 
contention. 
DB2 will try to notify WLM about resource contention to extent it knows about 
dependencies. Based on such notifications DB2 and WLM support
- Regular "enqueue promotion" and short term promotion . Both promote the 
holder of the lock to an elevated dispatch priority, increasing its chances to 
get dispatched. Search for "Sysevent ENQHOLD")
- Chronic contention. Elevates the resource holder to the highest dispatch 
priority of any waiter. (Search for IWMCNTN).

Still there can be situations where neither DB2 (and certainly no one else) 
knows the dependencies. For such cases the blocked workload support provides 
the capability that *any* address space that has been blocked -not dispatched- 
for a given time will be granted one time slice. That's a very small amount of 
processor time and it is handed out *independently* of any contention. Yet it 
is proven to be a very effective way to address DB2 latch contention. (Only 
latches typically gate such a short path that the contention can be resolved 
through one or a few of such "trickles".)
See the ENV and BLWLINTHD IEAOPTxx parameter (BLWLTRPCT is almost never the 
limiting fact).
Searching for OA44526 will give you a good list of recommendations.

DB2 and GRS locks are unrelated (except for allocation related ones).

Horst Sinram - STSM, IBM z/OS Workload and Capacity Management

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

Re: Documentation in non-English languages?

On 2017-02-06, at 06:27, R.S. wrote:

> W dniu 2017-02-06 o 14:03, Sean Gleann pisze:
>> 
>> Ok, I've only done a cursory search, but can anyone tell me if IBM
>> documentation ( the 'old-style' manuals and the redbooks are available in
>> languages other than English.
>> My search (such as it was) does not lead me to think so...
> 
> Redbooks - no. Official documentation - yes, there were non-English versions.
> However I remember opinion of some lady from South America: they preferred 
> English documentation, because Spanish translation was horrible.
>  
Probably done by a computer.  And not Watson.  (See the SuperBowl ad?)

-- gil

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

Re: Eight-character TSO Userid Support

On 2017-02-06, at 08:29, John McKown wrote:

> On Mon, Feb 6, 2017 at 8:45 AM, Edward Gould 
> wrote:
>> 
>> Thanks, I wonder how much  IBM and user code is going to have to change to
>> allow this?
>>  
I suppose it depends on whether your installation exploits the feature.

DSN prefix?  SUBMIT?  OUTPUT?  (I'd prefer to see SUBMIT modified to
relax the F80 limit.)

> Very true. I know of a lot of control block which look something like:
> 
> USERID   DS 0CL8
> USERIDL  DS FL1
> USERIDV  DS CL7
>  
Why in that order rather than the reverse?

All in all, it's underreaching to break compatibility for a
15% increase.  While 8 is a pervasive enterprise convention,
many OSes (Linux? OS X? (I just succeeded with 32)) allow far
more.  Better to allow a long login name to map to a short UID.

-- gil

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

Re: DB2 Locks and WLM Blocked Workload Support?

2017-02-06 Thread Greg Dyck


On 2/6/2017 11:46 AM, Peter Hunkeler wrote:

- Are the "DB2 latches" implemented as GRS latches?
- Are row, page, tables space locks actually DB2 latches? In other words, would 
WLM be able to recognize a low priority job holding some DB2 locks is causeing 
delay so it can promote it?
- What have IRLM and its lock structures to do with GRS latsches, if anything?
- Does DB2 inform WLM about resource lockers, so WLM can possibly promote them?


- DB2 does not use GRS latches.  It has it's own internal latch manager.
- Row, page, and table space locks are managed by IRLM for DB2.
- IRLM does not use GRS latches.  It has it's own internal latch manager.

DB2 *will* communicate internal latch contention information to WLM.

IRLM *will* communicate lock and internal latch contention information 
to WLM.


Communication of contention information for WLM to take action with is 
not perfect.  There are windows where sufficient information does not 
exist about the requestors.  To cover these windows, WLM Blocked 
Workload support should always be enabled.


Regards,
Greg

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

Re: DB2 Locks and WLM Blocked Workload Support?

2017-02-06 Thread Lizette Koehler

If you have not done so, you might also want to post to the DB2 List who may 
have more experience.

To join, if you have not so, go to IDUG.ORG

Lizette


-Original Message-
>From: "van der Grijn, Bart (B)" 
>Sent: Feb 6, 2017 11:09 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: DB2 Locks and WLM Blocked Workload Support?
>
>Quick search yielded the following, which might help with some of your 
>questions: 
>https://www.toadworld.com/platforms/ibmdb2/b/weblog/archive/2013/04/22/db2-locking-part-3-locks-versus-latches
>and
>http://www-01.ibm.com/support/docview.wss?uid=swg1PM54608
>
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
>Behalf Of Peter Hunkeler
>Sent: Monday, February 06, 2017 12:47 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: DB2 Locks and WLM Blocked Workload Support?
>
> 
>Cross-posted from DB2-L
>
>
>DB2 is not my strength, so please bear with me.
>
>
>I understand that DB2 serializes access to its resources with various types of 
>locks. For access to data, some of them are row locks, page locks, tablespace 
>locks.
>
>
>WLM's "blocked workload support" can help to reduce resource contention by 
>giving low priority, resource holding work a CPU burst, so it may release the 
>resource it held.
>
>
>In the context of DB2, the doc talks about "DB2 latches" with which WLM may be 
>able to help. 
>
>
>Some (vague) questions. High level answers are sufficient.
>
>
>
>
>- Are the "DB2 latches" implemented as GRS latches?
>
>- Are row, page, tables space locks actually DB2 latches? In other words, 
>would WLM be able to recognize a low priority job holding some DB2 locks is 
>causeing delay so it can promote it?
>
>
>- What have IRLM and its lock structures to do with GRS latsches, if anything?
>
>
>- Does DB2 inform WLM about resource lockers, so WLM can possibly promote them?
>
>
> 
>Pointer to some documentation if I can answer myself by RTFM is appreciated.
>
>
>--
>Peter Hunkeler

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

Re: BSAM vs QSAM (and SORT).

On 2017-02-06, at 07:22, R.S. wrote:
> 
> It's worth to mention that performance of reverse processing dataset on real 
> tape is worse than horrible.
> And IMHO it's not argument for using virtual tapes but for not using datasets 
> on tape for applications. Tapes are for backup and ML2.
>  
I had understood that old-fashioned SORT with SORTWK on tape employed
read backwards very effectively.  Perhaps the SORT expert will jump in:
https://en.wikipedia.org/wiki/Oscillating_merge_sort

It was spectacular to watch.  Are the data un-reversed by hardware,
firmware, or software?

On 2017-02-06, at 10:24, Binyamin Dissen wrote:

> Also, reading a PDS member by member requires BPAM (which is really BSAM).
> 
Which was our motivation, when I was in a small group supporting a FOSS
compiler and runtime library, for implementing BPAM and BSAM but not
QSAM.  Once we had the BPAM interface, most of the interface could likewise
be used for BSAM.

Ironically, not burdened by the extreme storage constraints of OS/360, our
compiler eschewed most of BPAM.  At a COPY-type operation we simply opened
another DCB, processed the member to the end, then popped back to the parent
member; no NOTE or POINT involved.  Worked great on MVS; not at all on
CMS "OS Emulation".

-- gil

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

Re: DB2 Locks and WLM Blocked Workload Support?

2017-02-06 Thread van der Grijn, Bart (B)

Quick search yielded the following, which might help with some of your 
questions: 
https://www.toadworld.com/platforms/ibmdb2/b/weblog/archive/2013/04/22/db2-locking-part-3-locks-versus-latches
and
http://www-01.ibm.com/support/docview.wss?uid=swg1PM54608


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Hunkeler
Sent: Monday, February 06, 2017 12:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: DB2 Locks and WLM Blocked Workload Support?

 
Cross-posted from DB2-L


DB2 is not my strength, so please bear with me.


I understand that DB2 serializes access to its resources with various types of 
locks. For access to data, some of them are row locks, page locks, tablespace 
locks.


WLM's "blocked workload support" can help to reduce resource contention by 
giving low priority, resource holding work a CPU burst, so it may release the 
resource it held.


In the context of DB2, the doc talks about "DB2 latches" with which WLM may be 
able to help. 


Some (vague) questions. High level answers are sufficient.




- Are the "DB2 latches" implemented as GRS latches?

- Are row, page, tables space locks actually DB2 latches? In other words, would 
WLM be able to recognize a low priority job holding some DB2 locks is causeing 
delay so it can promote it?


- What have IRLM and its lock structures to do with GRS latsches, if anything?


- Does DB2 inform WLM about resource lockers, so WLM can possibly promote them?


 
Pointer to some documentation if I can answer myself by RTFM is appreciated.


--
Peter Hunkeler

 

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

DB2 Locks and WLM Blocked Workload Support?

2017-02-06 Thread Peter Hunkeler


Cross-posted from DB2-L


DB2 is not my strength, so please bear with me.


I understand that DB2 serializes access to its resources with various types of 
locks. For access to data, some of them are row locks, page locks, tablespace 
locks.


WLM's "blocked workload support" can help to reduce resource contention by 
giving low priority, resource holding work a CPU burst, so it may release the 
resource it held.


In the context of DB2, the doc talks about "DB2 latches" with which WLM may be 
able to help.


Some (vague) questions. High level answers are sufficient.




- Are the "DB2 latches" implemented as GRS latches?

- Are row, page, tables space locks actually DB2 latches? In other words, would 
WLM be able to recognize a low priority job holding some DB2 locks is causeing 
delay so it can promote it?


- What have IRLM and its lock structures to do with GRS latsches, if anything?


- Does DB2 inform WLM about resource lockers, so WLM can possibly promote them?



Pointer to some documentation if I can answer myself by RTFM is appreciated.


--
Peter Hunkeler



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

Re: Eight-character TSO Userid Support

On Mon, 6 Feb 2017 08:45:28 -0600 Edward Gould 
wrote:

:>Thanks, I wonder how much  IBM and user code is going to have to change to 
allow this?

They can require/default a PROFILE NOPREFIX. This will address almost all
dataset issues.

Then the FIB commands will need some slight changes.

:>> On Feb 6, 2017, at 6:57 AM, Patrick Loftus  
wrote:
:>> Looks like 8 character TSO userid support in z/OS v2r3
:>> http://www-01.ibm.com/support/docview.wss?uid=swg1OA51203

--
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: HSM followup question

2017-02-06 Thread Richards, Robert B.

Glenn,

Thanks for the technology update! 

I somehow missed the enhancements in the last two releases (haven't held a 
storage mgmt. position for a while, but I happily installed those z/OS 
releases!). 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Glenn Wilcock
Sent: Monday, February 06, 2017 12:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HSM followup question

HSM uses the current values of the assigned management class to manage a data 
set.  So, any changes made to the values of a management class will be used the 
next time that HSM selects for processing any data sets assigned to that 
management class.

A data set may be assigned to a different management class.  In fact, in z/OS 
V2R1 and higher, the HSM class transition support can be used to change the 
management class, storage class and/or storage group based on policy (note that 
data class is excluded).  In z/OS V2R2, the HSM MIGRATE TRANSITION command can 
also be used.

Glenn Wilcock
DFSMShsm Architect

--
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: BSAM vs QSAM

Also, reading a PDS member by member requires BPAM (which is really BSAM).

On Mon, 6 Feb 2017 07:59:24 -0600 Ron Burr  wrote:

:>As far as I know, reading a physical sequential (or partitioned dataset 
member) in reverse order can only be done using BSAM (via the BSP macro). Not 
that many applications require that mode of processing. But if one does, well 
then, that appears to be the only option. Mind you, there are some restrictions 
inherent in using BSP, as the manual explains.
:>The COBOL manual states that you can process a QSAM tape dataset in reverse 
order by doing an OPEN REVERSED, but I suspect that the dataset will actually 
be processed using BSAM, not QSAM.

--
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: HSM followup question

2017-02-06 Thread Glenn Wilcock

HSM uses the current values of the assigned management class to manage a data 
set.  So, any changes made to the values of a management class will be used the 
next time that HSM selects for processing any data sets assigned to that 
management class.

A data set may be assigned to a different management class.  In fact, in z/OS 
V2R1 and higher, the HSM class transition support can be used to change the 
management class, storage class and/or storage group based on policy (note that 
data class is excluded).  In z/OS V2R2, the HSM MIGRATE TRANSITION command can 
also be used.

Glenn Wilcock
DFSMShsm Architect

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

Re: Eight-character TSO Userid Support

2017-02-06 Thread Patrick Loftus

I guess it would involved A LOT of changes for IBM, ISVs, and users.
I suppose it will be optionally enabled,vuntil z/OS v3r1 :)

Shouldn't the 2.3 preview be released about now?  Maybe other APARs will reveal 
other snippets.

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

Re: HSM followup question

2017-02-06 Thread Greg Shirey

I could be wrong, but I believe the point being made was that the Management 
Class assignment could be driven by the values of Data Class or Storage Class, 
but not Storage Group.   On the other hand, there are a lot of factors that can 
drive an MC assignment in addition to or in place of the DC or SC values.

Regards,
Greg Shirey
Ben E. Keith Company

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of retired mainframer
Sent: Sunday, February 05, 2017 1:41 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HSM followup question



> Based on this, MC can only set three ways: By DC, by SC or by the MC routine 
> itself.

Is this true now?  It used to be that only the corresponding ACS routine could 
set a class.
 


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

Re: Eight-character TSO Userid Support

2017-02-06 Thread John McKown

On Mon, Feb 6, 2017 at 8:45 AM, Edward Gould 
wrote:

> Patrick:
> Thanks, I wonder how much  IBM and user code is going to have to change to
> allow this?
> Ed
>

Very true. I know of a lot of control block which look something like:

USERID   DS 0CL8
USERIDL  DS FL1
USERIDV  DS CL7

-- 
Our calculus classes are an integral part of your education.

Maranatha! <><
John McKown

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

Re: Eight-character TSO Userid Support

2017-02-06 Thread Edward Gould

Patrick:
Thanks, I wonder how much  IBM and user code is going to have to change to 
allow this?
Ed
> On Feb 6, 2017, at 6:57 AM, Patrick Loftus  wrote:
> 
> Looks like 8 character TSO userid support in z/OS v2r3
> http://www-01.ibm.com/support/docview.wss?uid=swg1OA51203
> 
> --
> 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: BSAM vs QSAM


W dniu 2017-02-06 o 14:59, Ron Burr pisze:

As far as I know, reading a physical sequential (or partitioned dataset member) 
in reverse order can only be done using BSAM (via the BSP macro). Not that many 
applications require that mode of processing. But if one does, well then, that 
appears to be the only option. Mind you, there are some restrictions inherent 
in using BSP, as the manual explains.
The COBOL manual states that you can process a QSAM tape dataset in reverse 
order by doing an OPEN REVERSED, but I suspect that the dataset will actually 
be processed using BSAM, not QSAM.


It's worth to mention that performance of reverse processing dataset on 
real tape is worse than horrible.
And IMHO it's not argument for using virtual tapes but for not using 
datasets on tape for applications. Tapes are for backup and ML2.


--
Radoslaw Skorupka
Lodz, Poland






--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając 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
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

Re: HSM followup question

2017-02-06 Thread Richards, Robert B.

You are, of course, correct. I was not thinking of those already assigned and I 
know better. Good catch!

Bob

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: Monday, February 06, 2017 7:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HSM followup question

W dniu 2017-02-05 o 13:20, Richards, Robert B. pisze:
> [...]
> 1) Changing the MC only affects NEWLY CREATED datasets
No, MC change affect all datasets with the MC assigned.
Caution: there are two changes possible:
ALTER dataset NEW-MC  - change MC value for existing datasets.
some-MC modification - change of given MC parameters.
Both affect existing datasets.

-- 
Radoslaw Skorupka
Lodz, Poland

---
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając 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
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.

--
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: SFTP on z/OS

2017-02-06 Thread John McKown

On Sat, Feb 4, 2017 at 3:15 PM, scott Ford  wrote:

> Guys:
>
> I have a SSH question, we dont have a ICSF , do i need one to do SSH ? We
> want to do scp from Windows to
> z/OS  . I want stepping thru the ICSF stc doc and read about 'head
> 'dev/random' and its not working returning an error
>

I am running SSH on z/OS 1.12 without having ICSF running. It is a bit
more CPU intensive. In this case, the "/dev/random" device does not work,
but SSH basically doesn't use it in this case. At least, that has been my
experience.

>
> Scott
>
>

-- 
Our calculus classes are an integral part of your education.

Maranatha! <><
John McKown

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

Re: BSAM vs QSAM

2017-02-06 Thread Ron Burr

As far as I know, reading a physical sequential (or partitioned dataset member) 
in reverse order can only be done using BSAM (via the BSP macro). Not that many 
applications require that mode of processing. But if one does, well then, that 
appears to be the only option. Mind you, there are some restrictions inherent 
in using BSP, as the manual explains.
The COBOL manual states that you can process a QSAM tape dataset in reverse 
order by doing an OPEN REVERSED, but I suspect that the dataset will actually 
be processed using BSAM, not QSAM.

Ron Burr
GT Software

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

Re: HSM followup question


W dniu 2017-02-05 o 13:20, Richards, Robert B. pisze:

[...]
1) Changing the MC only affects NEWLY CREATED datasets

No, MC change affect all datasets with the MC assigned.
Caution: there are two changes possible:
ALTER dataset NEW-MC  - change MC value for existing datasets.
some-MC modification - change of given MC parameters.
Both affect existing datasets.


--
Radoslaw Skorupka
Lodz, Poland






---
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając 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
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

Re: BMC Products Licensing - CPU Serial, MIPS or both?

W dniu 2017-02-03 o 16:22, E Van Wyk pisze:

Hi,

I'm looking to find out if anyone knows if BMC products make use of CPU Serial alone or MIPS and CPU serial for it's licensing checks?

We're planning on adding MIPS to the system by moving to a higher config for an
additional LPAR but the added LPAR will have no BMC products and we currently
do not have a support contract and are not getting any information from
documentation. Some of our other product suppliers informed us their products
do check the amount of available MIPS but will still function normally, a
warning will just be issued.

The BMC products are on version 8.0.03 (Control O, M and T/M-Tape)

ControlM can be licensed per MIPS or per job submitted (# of job per day).
Licensing key depend on the licensing method, but IMHO none of them
checks MIPS value.

CPU serial is being checked by MIPS license.

BTW: that means you can upgrade your machine and ControlM will not stop
working, but it can be a license violation.

--
Radoslaw Skorupka
Lodz, Poland

---
Treść tej wiadomości może zawierać informacje prawnie chronione Banku
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość
włączając 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
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88.
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości
wpłacony) wynosi 168.955.696 złotych.

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

Re: Documentation in non-English languages?


W dniu 2017-02-06 o 14:03, Sean Gleann pisze:

Hello

Ok, I've only done a cursory search, but can anyone tell me if IBM
documentation ( the 'old-style' manuals and the redbooks are available in
languages other than English.
My search (such as it was) does not lead me to think so...


Redbooks - no. Official documentation - yes, there were non-English 
versions.
However I remember opinion of some lady from South America: they 
preferred English documentation, because Spanish translation was horrible.


--
Radoslaw Skorupka
Lodz, Poland






--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając 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
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

Re: HSM followup question


W dniu 2017-02-04 o 02:14, Lizette Koehler pisze:

We do lots of alter for mgmtclas.  We cannot alter Dataclass.


Yes, and no.
No - you cannot alter dataset parameters like LRECL or RECFM. You can 
change it as DC parameters, but existing dataset will be unaffected.


Yes - you can change DVC (dynamic volume count) and it affect existing 
datasets.


Another case - you can change CI/CA freespace in DC - it won't affect 
existing datasets.
However if you change freespace using ALTER vsam.cluster, then the 
parameters will be changed ...but still not for existing PART of the 
dataset, only for new records.



Regards
--
Radoslaw Skorupka
Lodz, Poland






--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając 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
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

Documentation in non-English languages?

2017-02-06 Thread Sean Gleann

Hello

Ok, I've only done a cursory search, but can anyone tell me if IBM
documentation ( the 'old-style' manuals and the redbooks are available in
languages other than English.
My search (such as it was) does not lead me to think so...

Sean

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

Re: Eight-character TSO Userid Support

2017-02-06 Thread Patrick Loftus

Looks like 8 character TSO userid support in z/OS v2r3
http://www-01.ibm.com/support/docview.wss?uid=swg1OA51203

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

Re: SFTP on z/OS

2017-02-06 Thread Jantje.

On Fri, 3 Feb 2017 07:58:24 -0600, Kirk Wolf  wrote:

>Standard SSH/SFTP doesn't support X.509 certificate's for authentication,

Doesn't it? I didn't know that...

>(z/OS OpenSSH does allow you to put SSH public and private keys in a Key
>Ring Certificate, but only the keys are used; the certificate and its
>signature are irrelevant.)

OK, so then I need a trustworthy channel to get me the public key. Still an 
issue of trust, but a different one, I expect.

Cheers,

Jantje.

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

Re: ZPDT usb issue after lunux update.

2017-02-06 Thread Itschak Mugzach

Binyamin, i think this mail is targeting Chad (bigendian)...

ITschakń

בתאריך 6 בפבר 2017 11:14,‏ "Binyamin Dissen" 
כתב:

> Everyone in IBM-Main?
>
> On Sun, 5 Feb 2017 21:02:10 -0600 Tim Full  wrote:
>
> :>If you're ever in Minneapolis, I owe you a beverage :)
>
> --
> 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
>

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

Re: ZPDT usb issue after lunux update.