Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Forum Index
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
Goto page Previous  1, 2
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message

Active Member

Joined: 06 Jul 2010
Posts: 690
Location: Whitby, ON, Canada

PostPosted: Tue Nov 05, 2013 12:13 am    Post subject:
Reply with quote

I have heard that some shops, (not the one that I work at) make no effort to retain the DBRM after the package has been bound.

Technically, once the package is bound the DBRM is no longer needed. If you need to Bind the package into another collection within the same DB2 subsystem, you can do a BIND copy.

Despite that, IMO the DBRM should be treated like gold, and should be managed in parallel with the underlying source code. That is the practice in the shop where I work, and I have never felt the need to recover the DBRM text from the catalog, even with older versions of DB2 where it was relatively easy to do.
Back to top
View user's profile Send private message


Senior Member

Joined: 11 Aug 2009
Posts: 1281
Location: Belgium

PostPosted: Tue Nov 05, 2013 8:41 pm    Post subject:
Reply with quote

Database request modules
The database request module (DBRM) is a data set that contains the SQL statements and host variable information that is extracted from the source program, along with information that identifies the program and ties the DBRM to the translated source statements. It becomes the input to the bind process.
The data set requires space to hold all the SQL statements plus space for each host variable name and some header information. The header information alone requires approximately two records for each DBRM, 20 bytes for each SQL record, and 6 bytes for each host variable.

For an exact format of the DBRM, see the DBRM mapping macros, DSNXDBRM and DSNXNBRM, in library prefix.SDSNMACS. The DCB attributes of the data set are RECFM FB, LRECL 80. The precompiler sets the characteristics. You can use IEBCOPY, IEHPROGM, TSOCOPY and DELETE commands, or other PDS management tools for maintaining these data sets.

Restriction: Do not modify the contents of the DBRM. If you do, unpredictable results can occur. DB2 does not support modified DBRMs.

In a DBRM, the SQL statements and the list of host variable names use the UTF-8 character encoding scheme.

All other character fields in a DBRM use EBCDIC. The current release marker (DBRMMRIC) in the header of a DBRM is marked according to the release of the precompiler, regardless of the value of NEWFUN.

Back to top
View user's profile Send private message

Global Moderator

Joined: 03 Oct 2009
Posts: 1789
Location: Bloomington, IL

PostPosted: Tue Nov 05, 2013 8:51 pm    Post subject:
Reply with quote

I presume Bind Manager is a pay-for-play option?
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2 All times are GMT + 6 Hours
Goto page Previous  1, 2
Page 2 of 2


Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Create view statement from SYSIBM.SYS... andrea DB2 7 Thu Aug 02, 2018 9:30 pm
No new posts SYSIBM Catlog tables to see DDL chang... rakesh17684 DB2 2 Fri Jun 08, 2018 3:43 am
No new posts ERM-Diagram of SysIBM-Catalog-Tables Auryn DB2 2 Fri Feb 17, 2017 6:22 pm
No new posts Can not find SQL statement of package... chaoj DB2 2 Wed Mar 11, 2015 12:00 pm
No new posts -551 on SYSIBM.SYSTABLES, SYSIBM.SYST... baramesh DB2 5 Mon Dec 23, 2013 6:29 pm

Back to Top
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us