Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1871

May 29th, 2015 14:00

PER BIT

Should the PER bit be set with AS/400??

5 Practitioner

 • 

274.2K Posts

June 2nd, 2015 15:00

thank you

465 Posts

May 31st, 2015 21:00

The restriction on PER for AS400 (thin) devices is documented in the SE array controls CLI product guide:

AS/400_D910_099 thin devices cannot be CKD metadevices, SAVE devices, or DATA devices. In addition, IBM i thin devices cannot have the following attributes:

• RCVRPNT_TAG

• ACLX

• SCSI3_persist_reserv

• DIF1

5 Practitioner

 • 

274.2K Posts

June 1st, 2015 04:00

These are not d910_099 devices these 2107-050 and I don't see any mention of this device type needing the PER bit or not.

5 Practitioner

 • 

274.2K Posts

June 1st, 2015 05:00

Building a new bin with the 2107-050 emulation does have the scsi persistent  bit enabled on the volumes by default.

465 Posts

June 1st, 2015 16:00

OK, are they thick or thin?

465 Posts

June 1st, 2015 17:00

For a thin AS400 device, the only valid emulation is AS/400_D910_099. So i guess you must be creating thick devices.

There is no restriction related to PER for thick AS400 devices. Leaving PER enabled is fine.

5 Practitioner

 • 

274.2K Posts

June 2nd, 2015 04:00

Okay thank you was there any place you found that so I could refer to?

465 Posts

June 2nd, 2015 15:00

There is no documented restriction (with the exception already listed here) on PER with AS400. I verified my response by checking a a running AS400 config at 5876 code.

465 Posts

June 2nd, 2015 21:00

Note that the restriction on PER in the array controls CLI product guide has been removed in the current version of the document.

No Events found!

Top