Re: Any idea? Dirmaint error by detach 123 disk(540RES)

2009-05-27 Thread Harder, Pieter
Hi, If you didn't touch the config then simply forcing and xautologging dirmaint will probably fix it. I you deleted the definition of minidisk 123 from the dirmaint directory entry, or the definition that may point to (eg maint 123) things get more complicated. If so come back to the communit

Re: Any idea? Dirmaint error by detach 123 disk(540RES)

2009-05-27 Thread Clovis Pereira
>> How can I fix this? Please. Help. On MAINT, DETACH 123 This command will restore the link: DIRM CP LINK * 123 123 MR If DIRMAINT reply returns RC=0 then try your commands again. Like this: DVHREQ2288I Your CP request for MAINT at * has been accepted. DVHCMS3868I DASD 0123 LINKED R/W; DVHREQ2

Re: Adabas from VM to z/Linux

2009-05-27 Thread Saulo Silva
Hi Andrew, I know about successful case from linux on system x , but since it works very well on linux it will work in system z also . Best regards, Saulo Silva 2009/5/25 Andrew Avramenko > Hello, > > > Does anyone have experience in migration of Software AG Adabas > database from VM to z/Lin

Tape drives for zLinux servers

2009-05-27 Thread Spann, Elizebeth (Betsie)
Hello VM/zLinux users, We are trying to identify the tape drive models that can be used natively by a zLinux server; i.e. FCP attached. I believe that the list includes TS1120 tape drives, 3592 J1A tape drives. What else, please? Do you use a tape library? Betsie --

Re: Tape drives for zLinux servers

2009-05-27 Thread Hall, Ken (GTS)
We're using 3592 drives, with 3494 library (TS3500), via FCP attach. There's a document from IBM that lists everything supported: ftp://ftp.software.ibm.com/storage/devdrvr/Doc/IBM_Tape_Driver_IUG.pdf -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf

Re: Tape drives for zLinux servers

2009-05-27 Thread Lee, Gary D.
We are using ts1120 drives in a 3494 library. Currently running tsm v5.4.4 on sles9 sp4. We will be moving to sles10 when tsm v6 is really ready. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: Linux on 390 Port [mailto:linux-...

Re: Adabas from VM to z/Linux

2009-05-27 Thread Barton Robinson
Make sure that "IF" there are additional CPU requirements, you measure them before committing to production. Some installations in the past have seen significant increases - SAG has made improvements, so don't take my word/experience as gospel, measure it... Saulo Silva wrote: Hi Andrew, I kno

Re: Tape drives for zLinux servers

2009-05-27 Thread Marcy Cortes
We have ULT3580-TD2 and ULT3580-TD4 (LTO2 and LTO4) in 3584 ATL libraries. These are incoming tapes for an application, not for backups. This runs on SLES 10 SP2 with the lin_tape drivers downloaded from IBM. Marcy "This message may contain confidential and/or privileged information. If you are

problem initializing token for crypto processor

2009-05-27 Thread Michael A Willett
We are having an issue initializing a token for crypto processor. We received the error below then updated to SLES10sp1 since we have test system that is at SLES10sp1 working without the error. We are still getting the error after updating the kernel to SLES10sp1. Has anyone run into this problem?

Re: problem initializing token for crypto processor

2009-05-27 Thread Mark Post
>>> On 5/27/2009 at 2:54 PM, Michael A Willett wrote: > We are having an issue initializing a token for crypto processor. We > received the error below then updated to SLES10sp1 since we have test > system that is at SLES10sp1 working without the error. I've never had a chance to experiment wit

Re: problem initializing token for crypto processor

2009-05-27 Thread Marcy Cortes
Found this from our WAS expert here: # check config things /usr/lib/pkcs11/methods/pkcsconf -t /usr/lib/pkcs11/methods/pkcsconf -i /usr/lib/pkcs11/methods/pkcsconf -s # "initialize token" SO default = 87654321 /usr/lib/pkcs11/methods/pkcsconf -c 0 -I # Enter the default & label it 'PCICAO'

Z10 2098 Q03 Experiences with Sles9 or Sles10

2009-05-27 Thread Shockley, Gerard C
Q: Has anyone experienced any issues migrating from z9 to a z10 (any issue or processor model) for s390x SLES9 or 10? SLES9 is at 2.6.5-7.282 SLES10 is at 2.6.16.60-0.37 TIA Gerard C. Shockley Boston University gsh...@bu.edu 617.353.9898 (w) 617.353.6171 (f) http://www.bu.edu/uis_web3

Re: Z10 2098 Q03 Experiences with Sles9 or Sles10

2009-05-27 Thread Ron Foster
Everything worked when we did it. Depending on your exact configuration, you may get some unexpected results. We finally attributed what was happening to NUMA effects of the z10. Ron --Original Message-- From: Shockley, Gerard C Sender: Linux on 390 Port To: LINUX-390@VM.MARIST.EDU Repl

Re: Z10 2098 Q03 Experiences with Sles9 or Sles10

2009-05-27 Thread Ayer, Paul W
We have sles 9's and 10's and also rhel 4.4 thru 5.3 systems and had no issues at all from z9 to z10 hardware changes. Paul -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shockley, Gerard C Sent: Wednesday, May 27, 2009 4:06 PM To: LINUX-390@VM.MA

sles11 zipl multipath /boot problem

2009-05-27 Thread Romanowski, John (OFT)
On a z10 I have a sles 11 with multipath /boot LUN and a separate multipath / LUN sles 11 Storage Guide says sles 11 supports a multipath /boot: "DM-MP is now available and supported for /boot and /root in SUSE Linux Enterprise Server 11." (Which I think means zipl can now write the scsi bootl

Re: Z10 2098 Q03 Experiences with Sles9 or Sles10

2009-05-27 Thread Marcy Cortes
No problems at all. We've had a z10 (2097) since early 08 with no issues. Be sure you pull the PSP 2098DEVICE from IBM. There are a couple of VM Apars that you might want to know about. Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or

Re: High interrupt rate

2009-05-27 Thread Alan Ackerman
I read through this thread. I see information about db2fmcd, which you say did not cause your problem. I don't see anything in the thread that tells me about the problem or fix to the kernel. Can you point me to information about the kernel problem? Just to confuse things, we have Red Hat, not Su