Recent content by legacy370

Right on, WMK. With the information you've supplied, I tried running the program with a runtime option, as follows: //JS0100 EXEC PGM=BADPRINT,PARM='/CBLQDA(OFF)' //WRONGPRT DD DSN=NBDNMS0.BADPRINT.RPTFILE, // DISP=(NEW,CATLG,DELETE), //...

I'm certain that the source and load are in synch, because I just compiled it as a test case. In other words, every program is behaving like this, even those compiled years ago. In looking at the sysout, I see that SMS is somehow allocating the file dynamically: IGD101I SMS ALLOCATED TO...

Here is a strange case, where we expect the program to abend, but it doesn't. Can anyone explain why? The program has SELECT RPTFILE ASSIGN TO RPTFILE. The JCL, by mistake, had //prtfile dd dsn=<whatever>. The program does an OPEN OUTPUT RPTFILE, and even writes records to the file, and...

In our environment, which is DB2 version 7 on OS/390, we add the phrase WITH UR to the end of the SQL statement. UR means uncommitted read. This is the so-called &quot;dirty read,&quot; that gives you data, even if that page is locked.

I had the same symptom with the same processor, and tried the same remedies. Finally, since the machine was still under warrantee, I took it to the manufacturer, who found a problem with the motherboard, which they replaced.

I want to bring out a point that you should be aware of: presuming that you're using ROWID for your identity fields, DB2 changes the ROWID whenever the table is loaded. Consequently, if you've inserted those original ROWID's into a child table, you'll need to update the child table with the...

Even with page-level locking, if you explicitly commit the update, DB2 should release the locks. Also, as implied in the first response, it might help to specify &quot;cursor stability&quot; rather than &quot;repeatable read&quot; as your isolation level. This is something the DBA would most...

We're using DB2 UDB for OS/390 V7 . An IBM mainframe, in other words. We reach DB2 from our Microsoft NT Server by using a product from IBM called DB2 Connect.

We're using DB2 UDB for OS/390 V7 Licensed Bookshelf. An IBM mainframe, in other words. We reach DB2 from our Microsoft NT Server by using a product from IBM called DB2 Connect.

We have a couple of web applications, written in VB and asp, that use both SQL Server and DB2. From an application developer's perspective, I'd say that SQL server is more flexible, and generally friendlier to use. However, nothing beats the performance of DB2. We have some queries that...

What you might be looking for is ROWID. Take a look at the following, from the IBM DB2 manual: A row ID is a value that uniquely identifies a row in a table. A column or a host variable can have a row ID data type. A ROWID column enables queries to be written that navigate directly to a row in...

It's my understanding that you can't use an ORDER BY when defining a view. As Hattusas remarked, you're free to use the ORDER BY when accessing the view.

One suggestion: on the queries, you can specify FOR FETCH ONLY WITH UR. The &quot;WITH UR&quot; will cause the query to do a &quot;dirty read,&quot; meaning that it will blast right through any locks and read the data anyway. &quot;FOR FETCH ONLY&quot; will cause your query to avoid taking any...

Cast the Varchar to a decimal. For example select * from fcm00.ic_umatrix where decimal(umat_keypart1) > 100

Using asp and accessing DB2 on an OS/390 computer, we've had great success with Cobol stored procedures. However, we find that we can't use ADO paging on recordsets returned from a Cobol stored procedure. The error we get says that &quot;bookmarking&quot; is not supported, when the asp tries to...