Hi peanut gallery friends, :-)
One of my users is a heavy batch Intertest user and received the
following message/abend:
IDMS DC999999L MODULE CAMRTPGM BLDL FAILED
Any of you have any idea what's going on here? I asked him to have the
Interest people open a problem, but I don't know if he did or will.
Inquiring minds want to know.
Dick
Richard Pierce
IDMS Database Administrator
Massachusetts Dept of Transportation, Information Technology
10 Park Plaza, Suite 7110
Boston, MA 02116
(617) 973-8911
richard.pierce@state.ma.us
www.mass.gov/massdot
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
z/os 1.11
"Does anyone know if IDMS Rel. 16 SP05 is z/OS 1.11 certified?
=20
Michael J. Barta
Mainframe Database || Infocrossing, a Wipro Company || 11707 Miracle
Hills Drive, Omaha NE, 68154|| ': 402.496.8564 ||7: 402.496.8676 || ::
michael.barta@infocrossing.com **Think Green - Please print
responsibly**
=20
Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or ""Protected Health Information,"" within the meaning of the regulations under the Health Insurance Portability & Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
z/os 1.11
"Does anyone know if IDMS Rel. 16 SP05 is z/OS 1.11 certified?
Michael J. Barta
Mainframe Database || Infocrossing, a Wipro Company || 11707 Miracle
Hills Drive, Omaha NE, 68154|| ': 402.496.8564 ||7: 402.496.8676 || ::
michael.barta@infocrossing.com **Think Green - Please print
responsibly**
Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or ""Protected Health Information,"" within the meaning of the regulations under the Health Insurance Portability & Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
OLQ Select index set
"Consider the situation:
Recordname : FSPR-VAFVAST
System-owned index : S-9999-783
Using OLQ I want to have the recordoccurrence of FSPR-VAFVAST where (VAF-RNR = 210002735)
Using GET statement it's quite simple:
GET FIR FSPR-VAFVAST WITHIN S-9999-783 WHERE SORT = 210002735
When I use the equivalent SQL statement :
SELECT * FROM FSPR-VAFVAST WHERE S-9999-783 AND VAF-RNR = 210002735
I get the errormessage:
OLQ 143005 08 Boolean conjunction (AND/OR/NOT) has non-bit operand.
Is the syntax incorrect or is it impossible to use index sets?
Schema definition of S-9999-783 is :
DIS SET S-9999-783
*+ ADD
*+ SET NAME IS S-9999-783
*+ ORDER IS SORTED
*+ MODE IS INDEX USING SIN-9999-783
*+ OWNER IS SYSTEM
*+ WITHIN AREA VAF-INDEX SUBAREA SYM-9999-783
*+ MEMBER IS FSPR-VAFVAST
*+ WITHIN AREA VAF SUBAREA SYMB-VAFVAST
*+ INDEX DBKEY POSITION IS 3
*+ MANDATORY AUTOMATIC
*+ KEY IS (
*+ VAF-RNR ASCENDING )
*+ DUPLICATES ARE LAST
*+ NATURAL SEQUENCE
*+ UNCOMPRESSED
*+ .
Kind regards,
Sibe Verbeek
ABN Amro bank
The Netherlands
0031-030-2260591
********************************* DISCLAIMER *********************************
This message (including any attachments) is confidential and may be privileged.
If you have received it by mistake please notify the sender by return e-mail and delete this
message from your system.
Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited.
Please note that e-mails are susceptible to change.
ABN AMRO Bank N.V, which has its seat at Amsterdam, the Netherlands, and is registered in
the Commercial Register under number 34334259, including its group companies,
shall not be liable for the improper or incomplete transmission of the information contained
in this communication nor for any delay in its receipt or damage to your system.
ABN AMRO Bank N.V. (or its group companies) does not guarantee that the integrity of this
communication has been maintained nor that this communication is free of viruses,
interceptions or interference.
-----------------------------------------------------------------------------
Dit bericht (inclusief de eventuele bijlagen) is vertrouwelijk.
Wanneer u dit bericht ten onrechte heeft ontvangen, dient u de afzender hiervan onmiddellijk
per kerende e-mail op de hoogte te brengen en dit bericht te verwijderen uit uw systeem.
Elk onbevoegd gebruik en/of onbevoegde verspreiding van dit bericht is niet toegestaan.
U wordt erop gewezen dat e-mail berichten aan wijziging onderhevig kunnen zijn.
ABN AMRO Bank N.V., statutair gevestigd te Amsterdam en ingeschreven in het handelsregister
van de Kamer van Koophandel onder nummer 34334259, en haar groepsmaatschappijen,
is niet aansprakelijk voor de onjuiste en onvolledige overdracht van de informatie in dit bericht
noch voor mogelijke vertraging in de ontvangst van dit bericht of schade aan uw systeem als
gevolg van dit bericht. ABN AMRO Bank N.V. (en haar groepsmaatschappijen) staat er niet
voor in dat de integriteit van dit bericht behouden is gebleven noch dat dit bericht vrij is
van virussen, niet is onderschept of vatbaar is geweest voor tussenkomst (door derden).
*****************************************************************************
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
Re: OLQ Select index set
"When we used the IDMS SQL option our queries needed to look something like =
this.
SELECT * FROM FSPR_VAFVAST WHERE ""S-9999-783"" AND VAF_RNR =3D 210002735
All IDMS record and field names had to use the underscore instead of hyphen=
and set names were double quoted.
Joe S Cates, Database Analyst II
Systems Architecture and Operations
Database Management/Unix Administration
Montgomery County Public Schools
Rockville, MD 20850
joe_cates@mcpsmd.org