Long time since last time i've used Hiperbatch (and problably i'm
missing
something), but i'll try to list some other issues with Hiperbatch :
a) CI size must be multiple of 4096
b) Does not work with shroptions 3 or 4 (VSAM)
c) Only QSAM (No Sort, IEBGENER) and VSAM sequential reading
d) Dataset can not be opened as I/O (otherwise will be removed from
storage)
e) If you want to use it with SORT, you can code EXIT15 and EXIT35
using QSAM
It used to work pretty fine (i believe it still does) but you have to
follow the rules...
Atenciosamente / Regards / Saludos
Ituriel do Nascimento Neto
Banco Bradesco S/A
4254/DPCD Alphaville
Engenharia de Software - Sistemas Operacionais Mainframes
Tel: 55 11 4197-2021 Fax: 55 11 4197-2814
-Mensagem original-
De: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Em nome
de Alex Tough
Enviada em: sexta-feira, 9 de novembro de 2007 16:00
Para: IBM-MAIN@BAMA.UA.EDU
Assunto: Hiperbatch revisited
Having some fun this week with Hiperbatch. I want to run one of our
largest VSAM clusters as a retained DLF object in RACF during batch run.
Asked Ops to run EXPORT, IMPORT to load into memory and everything
looked fine, so went to bed. Next morning, it turns out that the object
has been purged after being updated by job using BLSR.
Today I have proven to myself with a very simple Cobol programme that
subsequent use of BLSR will purge a retained object, but I can't see
from the MVS Hiperbatch Guide that this is working as expected :
Retained DLF objects continue to exist after the last user closes the
data set and must be deleted in one of the following ways:
* When the data set is recreated.
* When the data set is deleted or renamed.
* When the data set is updated by an access method (such as BSAM) that
does not support Hiperbatch.
* When the object is explicitly deleted
The data set hasn't been recreated, deleted, renamed or explicitly
deleted (I've tested that), so that just leaves being updated by an
unsupported access method. Using BLSR with VSAM, the access method is
still VSAM, certainly that's what I see in relevant SMF type 64 records.
Granted that it may well not be a good idea to access same cluster using
both BLSR and Hiperbatch and we can easily change our JCL.
Anybody seen this behaviour or have any thoughts ?
many thanks, Alex Tough
Systems Programmer, Express Gifts
--
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html
HTMLfont face=Tahoma size=1HRAVISO LEGAL brEsta mensagem é
destinada exclusivamente para a(s) pessoa(s) a quem é dirigida, podendo conter
informação confidencial e/ou legalmente privilegiada. Se você não for
destinatário desta mensagem, desde já fica notificado de abster-se a divulgar,
copiar, distribuir, examinar ou, de qualquer forma, utilizar a informação
contida nesta mensagem, por ser ilegal. Caso você tenha recebido esta mensagem
por engano, pedimos que nos retorne este E-Mail, promovendo, desde logo, a
eliminação do seu conteúdo em sua base de dados, registros ou sistema de
controle. Fica desprovida de eficácia e validade a mensagem que contiver
vínculos obrigacionais, expedida por quem não detenha poderes de representação.
HTMLfont face=Tahoma size=1HRLEGAL ADVICE brThis message is
exclusively destined for the people to whom it is directed, and it can bear
private and/or legally exceptional information. If you are not addressee of
this message, since now you are advised to not release, copy, distribute, check
or, otherwise, use the information contained in this message, because it is
illegal. If you received this message by mistake, we ask you to return this
email, making possible, as soon as possible, the elimination of its contents of
your database, registrations or controls system. The message that bears any
mandatory links, issued by someone who has no representation powers, shall be
null or void.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
