Sybase数据库技术,数据库恢复

• 首页
• 关于
• 订阅
• 归档
• 留言
• 标签
• 免费ASE测试环境
• 镜像站
• 恢复工具

CR:616923

CR Number:   616923 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 May 2010 Fixed Description page() in evaluate() and Find() function called on the main datwindow return wrong values if the DW has a nested report with autosize height set. 1. describe (evaluate('page()', 5)) 2. dw_2.find(pag=2, 1, dw_2.rowcount()) In a normal DW without nested report everything is fine. Workaround Description  Hence the following workarounds did work for the testcase: the describe/evaluate part: dw_2.setredraw(false) dw_2.scrolltorow(5) messagebox("", dw_2.describe(sle_1.text)) dw_2.scrolltorow(1) dw_2.setredraw(true) the find part: integer i, i_found, j for i=1 to dw_2.rowcount() step 1 dw_2.scrolltorow(i) for j=1 to dw_2.rowcount() step 1 if dw_2.find(sle_2.text, j, dw_2.rowcount()) = 1 then i_found = i end if exit next if i_found > 0 then exit end if next dw_2.scrolltorow(1) messagebox("", string(i_found)) this is some quick and dirty code i put together to show that this can be made working as expected. Not nice but it works for me though.

CR:616944

CR Number:   616944 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   Solaris 2.8 Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Oct 2010 Fixed Description Request for a PBVM 11.5.1 OF build 4675 or later for EAS 5.5 and 6.3 for Solaris 10

CR:617200

CR Number:   617200 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   Microsoft Windows 2003 Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 29 Mar 2010 Fixed Description 03/10/2010: Engineering confirmed that this behavior was changed in PB 11. Customers were complaining that the scroll bar was appearing automatically even when they had not checked the scroll bar property. This does not happen in Win32 behavior, so this was changed to have the same behavior. To get the scroll bar you need to check the scroll bar property. Customer has regression in how HTML is generated for a datawindow. The customer app uses EASever 5.5 and has jsps deployed to EAS. These jsps use their own PB component that uses Datastore.Describe("DataWindow.Data.HTML") to generate html that is displayed by the jsps. There app is large with many datawindows and they are seeing a regression in how their datawindows look: 1) Vertical scroll bar. They have a large text field, and in 10.5 html the field has a vertical scroll bar allowing access to all the text. There is no vertical scroll bar in 11.5.

CR:617344

CR Number:   617344 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 Mar 2010 Consult Complete Description Application is using PBDOM and doing a lot of with DW XML export/import. Randomly, app crashes only on runtime, the crash it's not always in the same place. It seems to point to xerces-c_2_6.dll

CR:617410

CR Number:   617410 Product Name:   PB Enterprise Product Component:   PB Web Services Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10 Feb 2010 Fixed 01 Mar 2010 Fixed Description Performance issue with .NET webservices Customer is observing poor performance using WebServices in Powerbuilder 11.5.1 he is using Webservices to bring back data files. The customer is seeing much better performance with their Java implementation.

CR:617622

CR Number:   617622 Product Name:   PB Enterprise Product Component:   DW Expression Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 21 Mar 2010 Fixed Description In PowerBuilder 10 and PowerBuilder 10.5 the datawindow trim function only removed spaces (char 20hex) But in PowerBuilder 11 and PowerBuilder 11.5 all white spaces are being removed space (char 20hex), carriage return, line feed, tab

CR:617798

CR Number:   617798 Product Name:   PB Enterprise Product Component:   DW DDDW Status:   Closed OS:   Microsoft Windows 2003 Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.5 08 Mar 2010 Fixed Description A crash is experienced with an application that is running under Citrix and Jaws. The crash occurs when accessing a dddw datawindow for which protectmode and some colour settings are set in script.

CR:618042

CR Number:   618042 Product Name:   PB Enterprise Product Component:   PB.NET WebForm Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Feb 2010 Not a Bug Description Multiple selection in a datawindow using the Shift key does not work in webforms. It does sort of work in Win 32. At least you can select two items but it did not allow me to select more than two as you would expect. So it seems not to work totally correctly even in Win 32. But it does not work at all in Webforms.

CR:618211

CR Number:   618211 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 Mar 2010 Fixed Description A jsp containing 2 webdatawindows, the itemchanged event fires when tabbing from column to column if column is a string column. This does not happen if the jsp contains only 1 webdw which is expected behavior.

CR:618495

CR Number:   618495 Product Name:   PB Enterprise Product Component:   System Runtime Functions Status:   Open OS:   Windows XP Original Version:   11.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Date() PowerScript function returns an unexpected date value in Japanese environment if the argument is an invalid date.

CR:618645

CR Number:   618645 Product Name:   PB Enterprise Product Component:   DW SaveAs Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 26 Mar 2010 Fixed Description Doing a datawindow SaveAs to Excel 2007 is very slow. Customer has 60,000 rows in a datawindow. Doing a dw_1.SaveAs("saveas_2003.xls", Excel!, true) takes only a second. But doing a dw_1.SaveAs("saveas_2007.xlsx", XLSX! , true) is taking almost an hour!

CR:618749

CR Number:   618749 Product Name:   PB Enterprise Product Component:   DB MS SQLServer Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Compare with PB6.5 MSS, it is reported that PB11.5x SNC dirver get slow performance with handle text column from MSSQL.

CR:618758

CR Number:   618758 Product Name:   PB Enterprise Product Component:   DW XML Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Feb 2010 Not a Bug Description OS: Windows XP SP3 Versions and Build #s Tested: PB 11.5.1_4675 and old PB 9.0_5507 Database/Driver File/Version: N/A Comments: When saving rows to xml, the decimal values entered in Portuguese (Brazil) decimal format are still saved in XML as US English decimal format. This is a regression when compared to old PB 9.0. Workaround Description  Maybe saving a string column instead of numeric one - may be not applicable to customer.

CR:618947

CR Number:   618947 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   Windows XP Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 Aug 2010 Fixed Description Currently there is no such property in WPF painter for DW, and so far only via a workaround the right behavior can be accomplished. Customer would eg. need to set Defaultlanguage to Hebrew!. Workaround Description  code in the itemfocuschanged event of the dw seems to work fine: string ls_col any la_rtl ls_col =this.getcolumnname( ) la_rtl = dw_1.describe(ls_col+".RightToLeft") //change the imput langauge if la_rtl = "1" then ActivateKeyboardLayout(1037, 0 ) else ActivateKeyboardLayout( 67699721, 0 ) end if

CR:619014

CR Number:   619014 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Mar 2010 Fixed 29 Mar 2010 Fixed Description When using multiple transactions and disconnecting one it disconnects the others. This didn't happen in build 4011, but it does now happen in later builds.

CR:619199

CR Number:   619199 Product Name:   PB Enterprise Product Component:   Language - Runtime Status:   Closed OS:   Linux Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 18 Oct 2010 Fixed Description PBVM doesnt support long data type from external function

CR:619227

CR Number:   619227 Product Name:   PB Enterprise Product Component:   PB.NET Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 01 Mar 2010 Workaround Description PB .Net assembly called from webservice under stress / load fails Getting intermittent exception: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array.

CR:619367

CR Number:   619367 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   Linux Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Oct 2010 Fixed Description GetChild doesn't work after calling the SetFullState function.

CR:619896

CR Number:   619896 Product Name:   PB Enterprise Product Component:   DB ODBC Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Special dbparm sequence needed when selectblob and MS ODBC. Whenever a SELECTBLOB statement is executed, the user is prompted to select the DSN. Does not work: sqlca.DBPARM = "DisableBind=1,ConnectString='DSN=myServer;UID=sa;PWD='" Works: sqlca.DBPARM = "ConnectString='DSN=myServer;UID=sa;PWD=',DisableBind=1" Solution is to move DisableBind at the end of the string. Same repro steps give no problem with ASA. Workaround Description  Solution is to move DisableBind at the end of the string.

CR:619925

CR Number:   619925 Product Name:   PB Enterprise Product Component:   WPF Runtime Status:   Closed OS:   Windows XP Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Nov 2010 Workaround Description When calling a method on a .NET assembly that returns a string, the following error results: Error: Exception thrown has not been handled System.AccessViolationException at line xx in event clicked of object cb_1 Problem only happens on Vista and Windows 7. Works ok on winxp

CR:620084

CR Number:   620084 Product Name:   PB Enterprise Product Component:   DB Sybase System Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Mar 2010 Fixed Description The default value of TrimSpaces=1 removes the leading spaces when using the ASE driver. Calling a stored procedure that will return a string and the string value has leading spaces. The ASE driver appears to remove the spaces. Works ok with the SYC driver

CR:620313

CR Number:   620313 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Closed OS:   Vista Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Mar 2010 Fixed Description Various problems when trying to make changes in the column specifications of datawindows in the datawindow painter.

CR:620642

CR Number:   620642 Product Name:   PB Enterprise Product Component:   PB.NET WebForm Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description When running a webform application, the network service (w3wp) occupies the memory. After logging out, the memory still remains. When many sessions are running a web form application and logging out, MemUsage continues to increase until 'The Server is busy' message appears. Then nothing responses.

CR:620819

CR Number:   620819 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Mar 2010 Fixed Description The customer migrated from an early version of PB 8 (8.0.2) to 11.5. They notice that clicking into fields on a newly inserted row in datawindows now takes much longer to enable them to enter data. In PB 8 they click on fields and instantly the cursor is in the field and they can start typing. But in 11.5.1 there is 3 second delay before the cursor appears and they can start typing. We were able to reproduce the fast behavior in an early version of PB 9 (9.0). But later versions of both 8 and 9 had a similar delay as 11.5.1 does. We suspect that the regression started sometime between 9.0 and 9.0.3, and 8.0.2 and 8.0.4. The customer is only seeing it now for the first time as they went from 8.0.2 to 11.5.1.

CR:620835

CR Number:   620835 Product Name:   PB Enterprise Product Component:   Window - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0 26 Apr 2010 Fixed Description A jre is deployed and resides in the same directory as an application executable and the system environment variable JAVA_HOME is set, the jdk from the JAVA_HOME is getting loaded. The issue is the customer has other (non pb) applications that rely on the JAVA_HOME to run and customer wants the jre that resides in the pb application executable directory to get loaded. Tried PBJRE_NOTUSECURRENT in the pb.ini jvm_version.exe jre -bin -lib

CR:620886

CR Number:   620886 Product Name:   PB Enterprise Product Component:   DB Oracle Status:   Closed OS:   Windows XP Original Version:   11.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Mar 2010 Fixed Description PB11.2 Oracle10g Driver does not support RPC information from DB link.

CR:620943

CR Number:   620943 Product Name:   PB Enterprise Product Component:   PB.NET Status:   Open OS:   Windows XP Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Allow PB nvo deployed as assembly to be thread-safe Currently they are not threadsafe. Workaround Description  Take a look at CR 619227, and a workaround if the assembly is called from a webservice. The calling program needs to take care of the threading : [WebService(Namespace = "http://tempuri.org/")] [WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)] [ToolboxItem(false)] public class Service1 : System.Web.Services.WebService { private static object _locker = new object(); [WebMethod] public String ThreadTest() { String username = ""; lock (_locker) { tieto.sybase.n_testthread nt = new tieto.sybase.n_testthread(); tieto.sybase.n_testreq res = nt.fortest(); username = res.getusername(); } return username; } }

CR:620973

CR Number:   620973 Product Name:   PB Enterprise Product Component:   DW Display Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 May 2010 Fixed Description When the dddw has a column in the detail band and the height of the band is set to 0, autosize height property is set, and the visible property is evaluated by expression, the dropdown simply does not show its contents.

CR:621005

CR Number:   621005 Product Name:   PB Enterprise Product Component:   DB DirectConnect Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Nov 2010 Workaround Description When creating a datawindow using the PBDIR driver and using the Access Services gateway, the datatype mapping is incorrect. A timestamp column is being converted to char(26). A char(3) column is converted to decimal(1) and char(9) is being converted to date. A smallint converted to long and date converted to time. RESOLUTION: DBParm of DBGatewayUDT='yes' resolved datatype mapping issue.

CR:621422

CR Number:   621422 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   Linux Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Dec 2010 Fixed Description Service Component fails to instantiate another component when path is too long.

CR:621815

CR Number:   621815 Product Name:   PB Enterprise Product Component:   DB ODBC Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.5 13 Jan 2014 Fixed Description PowerBuilder with ODBC connection to Informix When binding is enabled (DisableBind=0), strings are truncated when passed to the ODBC driver.

CR:621820

CR Number:   621820 Product Name:   PB Enterprise Product Component:   PB Web Services Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Apr 2010 Fixed 21 Mar 2014 Added to user documentation Description Calling a webservice using the .Net engine and the SoapConnection object. They intermittently get the error message: "The underlying connection was closed: A connection that was expected to be kept alive was closed by the server."

CR:621824

CR Number:   621824 Product Name:   PB Enterprise Product Component:   WPF DW Painter Status:   Open OS:   MS Windows NT 4.0 Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Add an option "Show RightToLeft property" and add this property to properties view for DataWindow

CR:621888

CR Number:   621888 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Apr 2010 Duplicate Description Customer upgraded to PB 11.5.1 (build 4608) and now datawindow.update() does not insert data into the database in certain scenerio. This worked in PB 11.5.1 (build 4566)

CR:621956

CR Number:   621956 Product Name:   PB Enterprise Product Component:   PB Web Services- NVO deployment Status:   Closed OS:   Windows XP Original Version:   11.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Apr 2010 Fixed Description When the update user function defined by .Net WSV NVO is called from DataWindow, the updated value is not applied to Database.

CR:621985

CR Number:   621985 Product Name:   PB Enterprise Product Component:   Menus - Runtime Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description MDI application with contemporary style menu and toolbar The toolbar background color becomes gray when ChangeMenu is called in the open event of a sheet that has no menu attached at designtime. The issue did not happen when the ChangeMenu call was posted.

CR:621999

CR Number:   621999 Product Name:   PB Enterprise Product Component:   Documentation Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Nov 2010 Fixed Description The datawindow object provides crosstab.properties. In the DataWindow Reference Guide, Chapter 3 it explains what each one of these crosstab properties are (Columns,Rows, SourceNames,StaticMode and Values). Under the 'See also' section, I think it should reference: see the Table.properties for details on the Table.CrossTabData. In the online help, select crosstab under the 'Index' tab. Select the Crosstab.property DataWindow Object property. It should be noted on that window that there is also a Table.CrosstabData property. Or provide a link under the 'See Also' commandbutton.

CR:622306

CR Number:   622306 Product Name:   PB Enterprise Product Component:   DB Painter Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Cannot use a global function in a validation rule with the DB painter.

CR:622347

CR Number:   622347 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Apr 2010 Fixed Description When using datawindow.data.html to display data in a browser and the datawindow is using the bold font, column data is getting truncated. The nv_remote_datawindow/generate calls the datawindow.data.html

CR:622697

CR Number:   622697 Product Name:   PB Enterprise Product Component:   DW Painter Status:   Open OS:   Windows 7 Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description When in the datawindow painter on windows 7 and trying to add a second retrieval argument the follow error appears: Column 2 has an invalid name and/or length If a existing dw has two arguments and you try to retrieve, the window 'Specify Retrieval Arguments' don't show the second argument. It just shows a blank.

CR:622858

CR Number:   622858 Product Name:   PB Enterprise Product Component:   WPF Compiler Status:   Open OS:   Windows 2008 Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Enhancement Request to provide options to be able to deploy a PBL to assembly (not only NVO's)

CR:622864

CR Number:   622864 Product Name:   PB Enterprise Product Component:   Edit Mask Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Enhancement Request: Be able to use expressions for the editmask mask property so that different masks can be used for different rows.

CR:623072

CR Number:   623072 Product Name:   PB Enterprise Product Component:   DW Display Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Apr 2010 Fixed Description A DataWindow contains overlapping columns in the detail band with mixed right and left allignment and transparent background. But when calling SelectRow some of the columns become hidden as if the column no longer is transparent.

CR:623100

CR Number:   623100 Product Name:   PB Enterprise Product Component:   DB OLE DB Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 26 Jul 2010 Consult Complete Description Customer is experiencing a serious performance problem with OLE DB using SQLNCLI10 as a provider. ServerCursor = 'NO' in pbdob ini file and Block setting to 1000, do not seem to help. Customer has set the above in the [Microsoft SQL Server] section of hispbodb115.ini file. We have checked to make sure it is set in the copy in the following directory(actually he has set it in every copy of pbodb115.ini on his machine) C:\Documents and Settings\psteinha\Local Settings\Application Data\Sybase\PowerBuilder 11.5 His datawindow has six nested reports and we have not been able to reproduce the time difference in a small report. I did a small analysis of the first 15 fetchs in each of the logs and the total times are as follows: SQLNCLI10 = 354.943 ms # 1 = 189.700 ms # 15 = 354.943 ms SQLOLEDB = 149.538 ms #1 = 210.285 ms # 15 = 359.823 ms SQLODBC = 108.953 ms # 1 = 284.037 ms #15 = 392.990 ms To get elapsed time I subtracted #1 from #15. While the SQLOLEDB takes longer than ODBC, SQLNCLI10 takes more than three times as long as ODBC. Customer insists that these results can be replicated over and over.

CR:623266

CR Number:   623266 Product Name:   PB Enterprise Product Component:   OLE - Active X - OCX Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description PB crashes when inserting an OLE control in a window.

CR:623428

CR Number:   623428 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 06 Apr 2010 Not a Bug Description The Page() and PageCount() functions in an expression are not displaying correctly in a treeview datawindow at runtime in a window. They are correct in PrintPreview and when printed. But in the window it always displays Page 1 of 1. By contrast they do display correctly in a tabular datawindow.

CR:623571

CR Number:   623571 Product Name:   PB Enterprise Product Component:   DB Sybase System Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Using sybcsi APIs to archieve encrypt/decrypt password in CTLIB

CR:623600

CR Number:   623600 Product Name:   PB Enterprise Product Component:   PB.NET DW Status:   Closed OS:   Windows XP Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Apr 2010 Fixed Description Using SetItem to set the text of an autosizeheight column in PB 12 .NET does not resize the column. Works in PB Classic.

CR:623634

CR Number:   623634 Product Name:   PB Enterprise Product Component:   Application Painter Status:   Closed OS:   Windows XP Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Apr 2010 Fixed Description With the application object open you should be able to drag a window object from the system tree to the open event of the application object (it should drop the window name). In pb 12 build 6013 I can't. Interestingly I can drag a dataobject, but not a window.

CR:624016

CR Number:   624016 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Apr 2010 Fixed 09 Jun 2010 Fixed Description If in a DataWindow an expression is used to enable the Tooltip of a column, then sometimes the tooltip of a column may still appear while it is disabled according to the expression.

CR:624048

CR Number:   624048 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 May 2010 Fixed Description The customer has a report and only wants to see the header on the first page. It's a large header and he wants all the detail rows to move up and into the empty space vacated by the header and allow more rows to be displayed on all pages > 1. The main part of the header is a nested report and an expression for it's height sets it to zero if it is not page 1. This works and the header disappears on pages > 1. The column text headers have an expression for the y value to move them up into the space left by the zero height nested report on pages > 1 and that works great. The final step is to set the header band to Autosize height, to move it up tight under the column header text. But this fails and all pages have the same header height. Pages after 1 have a large blank space that the header should move up into. A second problem with this is once the header band is set to autosize and the datawindow is closed, PB crashes when you attempt to re-open the datawindow in the painter.

CR:624192

CR Number:   624192 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description PowerBuilder with EAS 6.3 When there are no IIOP connections available, then a PB ORB connection should block until a listener thread becomes available. But the PB ORB stays blocked until a timeout occurs.

CR:624202

CR Number:   624202 Product Name:   PB Enterprise Product Component:   ORCA Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 29 Apr 2010 Fixed Description Orcascript is crashing on a winform full rebuild: Invalid Pointer Read on msvcr71?wcscpy8 In the orcascript log file, it appears it is on the cm_rebuild_application(CM_REBUILD_FULL).

CR:624223

CR Number:   624223 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Mar 2010 Not a Bug Description In PB 11.5 public CONSTANT instance varibles are not included in the easerver 5.5 proxy object. They were in PB 9. public CONSTANT string is_exposemeconstantly='exposeme!'

CR:624231

CR Number:   624231 Product Name:   PB Enterprise Product Component:   PB Web Services Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Apr 2010 Not a Bug Description PowerBuilder application uses third party .NET web services. It works with PB build 2506, but fails on all builds after 2506. Customer was trying to upgrade to latest EBF to see if webservices bug fix would help his performance problems.

CR:624548

CR Number:   624548 Product Name:   PB Enterprise Product Component:   Library Painter Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description In the library painter when you regenerate a number of objects together and an object fails to regenerate due to an error then status "Succeeded" can be reported instead of the number of errors.

CR:624635

CR Number:   624635 Product Name:   PB Enterprise Product Component:   DB Oracle Status:   Closed OS:   Windows XP Original Version:   11.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Apr 2010 Fixed Description 'for update' cursor for Oralce causes a memory leak.

CR:624799

CR Number:   624799 Product Name:   PB Enterprise Product Component:   Installation Status:   Closed OS:   Windows XP Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Apr 2010 Fixed Description * EN 5/19/10 New command line switch -ex <filename> where the filename contains error numbers allows those error numbers to not be counted as errors. Specification for CR 624977 1. Document History and Approvals 1.1 Document Change History Date Version Changes Author 5/4/2010 0.1 Initial Version Eric Nilson Add a new row to this table for each new version. 1.2 Milestones and Approvals Milestone Who and Date for each Solution Approval Design Approval Code Review and Approval Test Plan and Unit Test Approval Check-In Approval 2. CR Description 2.1. Product - ECRTP 2.2. Customers Problem Description REQUEST: Customer is requesting the ability to not generate an error when the data in an element is either larger or smaller than the min/max values for the element. This relates to CMS processing, as length violations are not considered rejected transactions, but rather, Accepted with Errors. The preferred result of this RFE would be a runtime flag to turn this error reporting off. 3. Engineers Restatement of Customers Problem Customer wants to specify to not count error of less than min element length or greater than max element length. It is OK to not write any error messages to trace or LOG and to return a value of zero indicating no errors to calling program. The transaction will be placed in the good file if good bad processing is being done. But if a field is mandatory and empty, then this will still be counted as an error. If field is empty and not mandatory, it will not be counted as an error. The mandatory error number is different so this will be done as long as the mandatory error is not in the exception file. Customer needs this special processing for inbound only. Engineers Solution Description 4. Customer Impacts, If Any To do special error checking like this will cause a small performance hit. 5. Design This feature is for inbound maps and inbound EDI->EDI or XML-EDI,. It has not been implemented for OUTBOUND, but will work with every type of INBOUND including X12, EDIFACT, NCPDP, HL7 and XML. The customers request will be satisfied by a generic approach that can be used to allow customers to pick minor types of ECRTP Error Numbers of errors that they want to be passed through the system without counting as an error. For the first implementation of this feature, the types of errors that are going to be passed through are the types of non-fatal errors that occur during mapping or rule processing. If the user places a Fatal Error number that causes ECRTP to abort and return a error code of 5, ECRTP will still abort and return an error code of 5, but the Error will not be written to TRLOG and will only be written to the TRACE file. A compliance map has a rule that states if Error, abort transaction, which means that if any error occurred during the processing of that transaction then the processing is aborted. The types of non-fatal errors that would hit this rule and cause an abort transaction in a compliance map will be able to be dismissed as not an error and not to cause an abort transaction. Also for a translation map, the mapping and rule edit type of errors can be changed to not count as an error. For this first release of this feature, such ECRTP errors involving incorrect Header segments (ISA, GS, ST) and Trailer segments (SE, GE, IEA) will be able to be dismissed as not errors and not written to TRLOG. But the ECRTP processing and return error code status will be the same as if the error was written to TRLOG and counted as an error.. And the same is true for Trade Partner errors and tal errors such as cannot open file. The discounting of the errors in the ex <filename> during mapping and rule processing will be done by setting a variable to 1 at start of mapping or rule processing and turning it back to a zero at end of mapping or rule processing. There are other more serious errors, where ECRTP will abort the transaction or the whole map run immediately after such a serious error occurs. These types of abort transactions will not be stopped by this CR. However, if one of these errors A new command switch, -ex <file name>, will be used to indicate that there is a file name that contains ECRTP Error numbers that are to be ignored. The file must consist of one 5 digit numeric error number on each line terminated by a new line. If this file cannot be opened, ECRTP will abort. If file line does not follow format of 5 digits new line, ECRTP will abort. The ex <file name> switch is required, but the file name does not have to exist on the disk if it was passed in as a MEMIOSTRUCT parameter. typedef struct { char *filename; char **paddr; long *pbytes; long *pbuflen; } MEMIOSTRUCT; When an Error occurs with an error number that matches an error number in the error exception file name, then the Error will be written to the TRACE File but not the LOG File. For example, if 1294 was in the exceptin file, theninstead of a trace message "(1294) ERROR: Maximum Length %d of EDI record exceeded" There will be a message " (DISM ) ERROR: Maximum Length %d of EDI record exceeded" The (DISM ) in the Trace File indicates that this error occurred but was dismissed (not counted as an error and not written to the LOG. At the end of a run, the message Number of Errors Dismmissed: NNN Will be added to the end of run summary if any errors have been dismissed. If only errors that were in the ex <filename> occurred during a run, then a value of 0 would be returned by ECRTP to indicate to the calling program that there were no errors. And EDI Transaction with no errors or only exception type of errors in the ex <filename> will be passed through as good transactions. 6. Summary of Technical Changes Functions Which and Why Globals & Structures Which and Why Error Message Changes The major changes were in the below files. STR.H long dism_err_cnt_in; /* Number of inbound errors not counted as errors due to -ex filename switch */ long dism_err_cnt_out; /* Number of edi->edi outbound errors not counted as errors due to -ex switch */ int itot_exceptions; /* size of array of exception error integer nuumbers pointed to by piexception_errs pointer */ int * piexception_errs; /* pointer to array of error integer nuumbers which should not count as errors */ INITMAP.CPP modified pr_args to process -ex filename and call new function load_exceptions() --------------- INITMAP.CPP new function load_exceptions /*------------------------------------------------------------------------- * load_exceptions - load ECRTP error numbers from a file that has 5 digits * followed by a newline *-------------------------------------------------------------------------*/ errmod.cpp modified pr_err() logic to not count error numbers that were loaded into memory from the exception file. new functions check_dismissed(char *msgnum,GLOBALSTRUTIN) /* checks to see if error number is in CVPTRIN piexception_errs */ long stat_dism_err_cnt(int delta, GLOBALSTRUTIN) /* adds count of dismised errs */ mstrseg.cpp new function ifinal_dism_msg.c - display final run dismissed error status 7. Test Plan Create a data file that contains edit errors and an error file with these edit error numbers and see if output is correct. Run same data file without the new ex <filename> and see if errors are reported. This was done using an from the DOS prompt with an old hippa EDI->EDI map with and without the -ex filename switch. And it worked as planned. wrmi32 C:\maps\hipaareg\errors.EDI -st "DSN=hipaareg" -sl "DSN=hipaareg" -o -k -z -l -dg C:\maps\hipaareg\837P -ex exfile.txt -tc 1000 -wx 1 -k -id 56 To test memory passing of the exception fi.le, on can load the exception file into a MSGVAR. Then use the MEMI Gateway Tab to set MSGVAR equal to the exact full or relative file name that will be used with the ex <filename> switch. I added the -ex <filename> switch to the pfs script. Below is a pfs file that I ran with same exfile.txt and map that I had used when testing wrmi32.exe from the DOS prompt. I was able to verify with the debugger that the exfile.txt was being read from the memory MSGVAR file that Gateway has passed in. hipaa_errors 5.2.1, 05/18/10 08:52:34 PM DSN=ORACLE10Driver;UID=SCOTT;PWD=wS+5der DSN=ORACLE10Driver;UID=SCOTT;PWD=wS+5der DSN=ECEDIGS C:\ecedigs51\blat.exe C:\ecedigs51\pfsFax.exe 4 1 1TraceOnOff 34 ||220 2 2LoadMemory 52 ||140||C:\maps\hipaareg\errors.edi||60|| 3 3LoadMemory 52 ||140||c:\maps\hipaareg\837p\exfile.txt||63|| 4 4RunMapIn 27 ||||-fn c:\maps\hipaareg\errors.edi -sl 12"DSN=hipaareg" -nz -dg c:\maps\hipaareg\837P -o -k -z -l -tc 1000 -ex c:\maps\hipaareg\837p\exfile.txt -wx 1 ||st||140||12"DSN=hipaareg"||sm||140||c:\maps\hipaareg\837p\exfile.txt||63|| And below is a trace file from the wsproces run of the pfs script. WSPROCES PC GATEWAY Version 5.2.1.0. - STARTED AT 21:46:04 ON 05/18/2010 - Processing script file: hipaa_errors.pfs INIT Successfully loaded Safepwd library INIT Successfully decrypted Trading Partner DSN INIT Successfully decrypted Log DSN INIT Successfully decrypted RunID DSN INIT Successfully Loaded the RTP Library Trace COMMAND: TraceOnOff ****** Line Number 1 ACTION: ON Trace COMMAND: LoadMemory ****** Line Number 2 ACTION: Obtained filename C:\maps\hipaareg\errors.edi supplied as string constant! ACTION: Size of file C:\maps\hipaareg\errors.edi: 1898 ACTION: Successfully read file C:\maps\hipaareg\errors.edi and stored buffer cbd018 in proces s var. Message[1] Trace COMMAND: LoadMemory ****** Line Number 3 ACTION: Obtained filename c:\maps\hipaareg\837p\exfile.txt supplied as string constant! ACTION: Size of file c:\maps\hipaareg\837p\exfile.txt: 6 ACTION: Successfully read file c:\maps\hipaareg\837p\exfile.txt and stored buffer cb48a8 in p rocess var. Message[4] Trace COMMAND: RunMapIn ****** Line Number 4 ACTION: Successfully decrypted PassWord for -ST ACTION: Creating MEMIO <3GetMSG>! ACTION: ELEMENT FILENAME (cbd7c0): file name ptr contains cbd7d0 ACTION: ELEMENT FN (cbd7d0) contains = c:\maps\hipaareg\837p\exfile.txt ACTION: ELEMENT PADDR (cbd7c4): data buffer ptr contains cbd8fc ACTION: ELEMENT MEMADDR (cbd8fc) : data buffer addr. = cb48a8 ACTION: ELEMENT PBYTES (cbd7c8): data size ptr contain cbd900 ACTION: DATASIZE (cbd900) : data size = 6 ACTION: ELEMENT PBUFLEN (cbd7cc): Buffer size ptr contains cbd904 ACTION: SHARED MEMORY 3GetMSG now ready for RTP or Message Queueing operations ACTION: ASSIGNED THIS SHARED MEMORY ID OF 2701 ACTION: Successfully decrypted PassWord for -SL ACTION: INRun Parameters = c:\maps\hipaareg\errors.edi -sl "DSN=hipaareg" -nz -dg c:\maps\hip aareg\837P -o -k -z -l -tc 1000 -ex c:\maps\hipaareg\837p\exfile.txt -wx 1 -st "DSN=hip aareg" -et "u:\calm_beth_ecgateway\WSPROCES\exe\Debug\TRACE" -id 2701 (address passed to rtp) 1015ee0 TRACE: Run Time Version: 5.2.1.4 INBOUND Run 20100518 214705 Run ID 2701 TRACE 1 Error Numbers in -ex exception file c:\maps\hipaareg\837p\exfile.txt TRACE: Reading ISA - Seg Delim 126 Elem Delim 042 Sub Delim 058 Test Ind P TRACE Opened:TP, AC=OFF TRACE Maximum Connections:64, Maximum Statements:0 TRACE DBMS Name :ACCESS, Version:04.00.0000 TRACE Cursor Commit Behavior = READ_ONLY TRACE: New tradepartner: 1075-1 TRACE: Looking.. Segment GS (control) TRACE: Exact Tradstat found for Tptnr 1075-1 Trans 837 Vers 004010X098A1 TstInd P ---LEVSEG TABLE--- [ 0]: Level: 30, Ordinal= 1, Seg ST , Max Loops= No Limit [ 1]: Level: 40, Ordinal= 1, Seg ST , Max Loops= No Limit [ 2]: Level: 50, Ordinal= 4, Seg NM1, Max Loops= 1 [ 3]: Level: 60, Ordinal= 6, Seg NM1, Max Loops= 1 [ 4]: Level: 70, Ordinal= 7, Seg HL , Max Loops= No Limit [ 5]: Level: 80, Ordinal= 10, Seg NM1, Max Loops= 1 [ 6]: Level: 85, Ordinal= 13, Seg REF, Max Loops= 8 [ 7]: Level: 90, Ordinal= 14, Seg REF, Max Loops= 8 [ 8]: Level: 100, Ordinal= 15, Seg REF, Max Loops= 8 [ 9]: Level: 110, Ordinal= 17, Seg NM1, Max Loops= 1 [10]: Level: 120, Ordinal= 21, Seg HL , Max Loops= No Limit [11]: Level: 130, Ordinal= 24, Seg NM1, Max Loops= 1 [12]: Level: 140, Ordinal= 28, Seg REF, Max Loops= 4 [13]: Level: 150, Ordinal= 29, Seg REF, Max Loops= 1 [14]: Level: 160, Ordinal= 30, Seg NM1, Max Loops= 1 [15]: Level: 170, Ordinal= 34, Seg NM1, Max Loops= 1 [16]: Level: 180, Ordinal= 37, Seg NM1, Max Loops= 1 [17]: Level: 190, Ordinal= 39, Seg HL , Max Loops= No Limit [18]: Level: 200, Ordinal= 41, Seg NM1, Max Loops= 1 [19]: Level: 210, Ordinal= 45, Seg REF, Max Loops= 5 [20]: Level: 220, Ordinal= 46, Seg REF, Max Loops= 1 [21]: Level: 230, Ordinal= 47, Seg CLM, Max Loops= 100 [22]: Level: 232, Ordinal= 91, Seg HI , Max Loops= 0 [23]: Level: 250, Ordinal= 48, Seg DTP, Max Loops= 1 [24]: Level: 270, Ordinal= 49, Seg DTP, Max Loops= 1 [25]: Level: 280, Ordinal= 50, Seg DTP, Max Loops= 1 [26]: Level: 290, Ordinal= 51, Seg DTP, Max Loops= 5 [27]: Level: 300, Ordinal= 52, Seg DTP, Max Loops= 10 [28]: Level: 310, Ordinal= 53, Seg DTP, Max Loops= 10 [29]: Level: 320, Ordinal= 54, Seg DTP, Max Loops= 1 [30]: Level: 330, Ordinal= 55, Seg DTP, Max Loops= 1 [31]: Level: 350, Ordinal= 56, Seg DTP, Max Loops= 1 [32]: Level: 360, Ordinal= 57, Seg DTP, Max Loops= 5 [33]: Level: 370, Ordinal= 58, Seg DTP, Max Loops= 5 [34]: Level: 380, Ordinal= 59, Seg DTP, Max Loops= 1 [35]: Level: 390, Ordinal= 60, Seg DTP, Max Loops= 1 [36]: Level: 400, Ordinal= 61, Seg DTP, Max Loops= 1 [37]: Level: 410, Ordinal= 62, Seg DTP, Max Loops= 1 [38]: Level: 420, Ordinal= 63, Seg DTP, Max Loops= 2 [39]: Level: 440, Ordinal= 66, Seg AMT, Max Loops= 1 [40]: Level: 450, Ordinal= 67, Seg AMT, Max Loops= 1 [41]: Level: 460, Ordinal= 68, Seg AMT, Max Loops= 1 [42]: Level: 470, Ordinal= 69, Seg REF, Max Loops= 1 [43]: Level: 480, Ordinal= 70, Seg REF, Max Loops= 1 [44]: Level: 490, Ordinal= 71, Seg REF, Max Loops= 1 [45]: Level: 500, Ordinal= 72, Seg REF, Max Loops= 2 [46]: Level: 520, Ordinal= 73, Seg REF, Max Loops= 1 [47]: Level: 530, Ordinal= 74, Seg REF, Max Loops= 3 [48]: Level: 540, Ordinal= 75, Seg REF, Max Loops= 1 [49]: Level: 550, Ordinal= 76, Seg REF, Max Loops= 1 [50]: Level: 560, Ordinal= 77, Seg REF, Max Loops= 1 [51]: Level: 570, Ordinal= 78, Seg REF, Max Loops= 1 [52]: Level: 580, Ordinal= 79, Seg REF, Max Loops= 4 [53]: Level: 590, Ordinal= 80, Seg REF, Max Loops= 1 [54]: Level: 600, Ordinal= 81, Seg REF, Max Loops= 1 [55]: Level: 610, Ordinal= 86, Seg CRC, Max Loops= 3 [56]: Level: 620, Ordinal= 87, Seg CRC, Max Loops= 3 [57]: Level: 630, Ordinal= 88, Seg CRC, Max Loops= 1 [58]: Level: 650, Ordinal= 89, Seg CRC, Max Loops= 1 [59]: Level: 660, Ordinal= 93, Seg CR7, Max Loops= 6 [60]: Level: 670, Ordinal= 95, Seg NM1, Max Loops= 3 [61]: Level: 690, Ordinal= 98, Seg NM1, Max Loops= 1 [62]: Level: 700, Ordinal= 101, Seg NM1, Max Loops= 1 [63]: Level: 710, Ordinal= 103, Seg NM1, Max Loops= 1 [64]: Level: 750, Ordinal= 107, Seg NM1, Max Loops= 1 [65]: Level: 760, Ordinal= 109, Seg SBR, Max Loops= 10 [66]: Level: 770, Ordinal= 111, Seg AMT, Max Loops= 1 [67]: Level: 780, Ordinal= 112, Seg AMT, Max Loops= 1 [68]: Level: 790, Ordinal= 113, Seg AMT, Max Loops= 1 [69]: Level: 800, Ordinal= 114, Seg AMT, Max Loops= 1 [70]: Level: 810, Ordinal= 115, Seg AMT, Max Loops= 1 [71]: Level: 820, Ordinal= 116, Seg AMT, Max Loops= 1 [72]: Level: 830, Ordinal= 117, Seg AMT, Max Loops= 1 [73]: Level: 840, Ordinal= 118, Seg AMT, Max Loops= 1 [74]: Level: 850, Ordinal= 119, Seg AMT, Max Loops= 1 [75]: Level: 860, Ordinal= 120, Seg AMT, Max Loops= 1 [76]: Level: 870, Ordinal= 124, Seg NM1, Max Loops= 1 [77]: Level: 880, Ordinal= 128, Seg NM1, Max Loops= 1 [78]: Level: 890, Ordinal= 131, Seg REF, Max Loops= 2 [79]: Level: 900, Ordinal= 132, Seg REF, Max Loops= 2 [80]: Level: 910, Ordinal= 133, Seg REF, Max Loops= 2 [81]: Level: 920, Ordinal= 134, Seg NM1, Max Loops= 1 [82]: Level: 930, Ordinal= 136, Seg NM1, Max Loops= 2 [83]: Level: 950, Ordinal= 138, Seg NM1, Max Loops= 1 [84]: Level: 960, Ordinal= 140, Seg NM1, Max Loops= 1 [85]: Level: 970, Ordinal= 142, Seg NM1, Max Loops= 1 [86]: Level: 1010, Ordinal= 144, Seg NM1, Max Loops= 1 [87]: Level: 1020, Ordinal= 146, Seg LX , Max Loops= 50 [88]: Level: 1030, Ordinal= 154, Seg CRC, Max Loops= 3 [89]: Level: 1040, Ordinal= 155, Seg CRC, Max Loops= 1 [90]: Level: 1050, Ordinal= 156, Seg CRC, Max Loops= 2 [91]: Level: 1060, Ordinal= 163, Seg DTP, Max Loops= 0 [92]: Level: 1070, Ordinal= 157, Seg DTP, Max Loops= 1 [93]: Level: 1080, Ordinal= 158, Seg DTP, Max Loops= 1 [94]: Level: 1100, Ordinal= 159, Seg DTP, Max Loops= 1 [95]: Level: 1110, Ordinal= 160, Seg DTP, Max Loops= 1 [96]: Level: 1130, Ordinal= 161, Seg DTP, Max Loops= 2 [97]: Level: 1140, Ordinal= 162, Seg DTP, Max Loops= 2 [98]: Level: 1160, Ordinal= 163, Seg DTP, Max Loops= 3 [99]: Level: 1190, Ordinal= 164, Seg DTP, Max Loops= 1 [100]: Level: 1200, Ordinal= 165, Seg DTP, Max Loops= 1 [101]: Level: 1210, Ordinal= 166, Seg DTP, Max Loops= 1 [102]: Level: 1220, Ordinal= 167, Seg DTP, Max Loops= 1 [103]: Level: 1230, Ordinal= 168, Seg DTP, Max Loops= 1 [104]: Level: 1240, Ordinal= 169, Seg DTP, Max Loops= 1 [105]: Level: 1250, Ordinal= 172, Seg REF, Max Loops= 1 [106]: Level: 1260, Ordinal= 173, Seg REF, Max Loops= 1 [107]: Level: 1270, Ordinal= 174, Seg REF, Max Loops= 2 [108]: Level: 1290, Ordinal= 175, Seg REF, Max Loops= 1 [109]: Level: 1300, Ordinal= 176, Seg REF, Max Loops= 1 [110]: Level: 1310, Ordinal= 177, Seg REF, Max Loops= 1 [111]: Level: 1320, Ordinal= 178, Seg REF, Max Loops= 1 [112]: Level: 1330, Ordinal= 179, Seg REF, Max Loops= 1 [113]: Level: 1340, Ordinal= 180, Seg REF, Max Loops= 4 [114]: Level: 1350, Ordinal= 181, Seg REF, Max Loops= 1 [115]: Level: 1360, Ordinal= 182, Seg REF, Max Loops= 1 [116]: Level: 1380, Ordinal= 183, Seg AMT, Max Loops= 1 [117]: Level: 1390, Ordinal= 184, Seg AMT, Max Loops= 1 [118]: Level: 1400, Ordinal= 185, Seg AMT, Max Loops= 1 [119]: Level: 1405, Ordinal= 191, Seg LIN, Max Loops= 25 [120]: Level: 1410, Ordinal= 194, Seg NM1, Max Loops= 1 [121]: Level: 1420, Ordinal= 197, Seg NM1, Max Loops= 1 [122]: Level: 1430, Ordinal= 199, Seg NM1, Max Loops= 1 [123]: Level: 1470, Ordinal= 203, Seg NM1, Max Loops= 1 [124]: Level: 1480, Ordinal= 205, Seg NM1, Max Loops= 1 [125]: Level: 1490, Ordinal= 210, Seg NM1, Max Loops= 2 [126]: Level: 1510, Ordinal= 213, Seg NM1, Max Loops= 4 [127]: Level: 1520, Ordinal= 215, Seg SVD, Max Loops= 25 [128]: Level: 1530, Ordinal= 218, Seg LQ , Max Loops= 5 TRACE Start Run of MAP HIPAA_837P_4010_50 TRACE: Level 10, Segment ISA (control) TRACE: Level 10->20, processing Segment ISA Before Rule- No: 10380 TRACE: Level 10->20, processing Segment ISA After Rule- No: 10080 TRACE: Level 20, Segment GS (control) TRACE: Level 20->30, processing Segment GS Before Rule- No: 10435 TRACE: Level 20->30, processing Segment GS After Rule- No: 10060 TRACE: Level 30, Segment ST (control) TRACE: Level 30->40, processing Segment ST Before Rule- No: 0 TRACE: Level 40, Segment ST (mapping) TRACE: Level 40, Segment ST 01 (mapping) TRACE: Level 40, Segment ST 02 (mapping) TRACE: Level 30->40, processing Segment ST After Rule- No: 1140 TRACE: Performing Rule 5030 TRACE: Performing Rule 13160 TRACE: Level 40, Segment BHT (mapping) TRACE: Level 40, Segment BHT01 (mapping) TRACE: Level 40, Segment BHT02 (mapping) TRACE: Level 40, Segment BHT03 (mapping) TRACE: Level 40, Segment BHT04 (mapping) TRACE: Level 40, Segment BHT05 (mapping) TRACE: Level 40, Segment BHT06 (mapping) TRACE: Level 40->40, processing Segment REF Before Rule- No: 815 TRACE: Level 40, Segment REF (mapping) TRACE: Level 40, Segment REF01 (mapping) TRACE: Level 40, Segment REF02 (mapping) TRACE: Level 40->40, processing Segment REF After Rule- No: 816 TRACE: Performing Rule 0 TRACE: Level 40->50, processing Segment NM1 Before Rule- No: 817 TRACE: Level 50, Segment NM1 (mapping) TRACE: Level 50, Segment NM101 (mapping) TRACE: Level 50, Segment NM102 (mapping) TRACE: Level 50, Segment NM103 (mapping) TRACE: Level 50, Segment NM104 (mapping empty data) TRACE: Level 50, Segment NM105 (mapping empty data) TRACE: Level 50, Segment NM108 (mapping) TRACE: Level 50, Segment NM109 (mapping) TRACE: Level 40->50, processing Segment NM1 After Rule- No: 818 TRACE: Performing Rule 504 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 1200 TRACE: Level 50->50, processing Segment PER Before Rule- No: 819 TRACE: Level 50, Segment PER (mapping) TRACE: Level 50, Segment PER01 (mapping) TRACE: Level 50, Segment PER02 (mapping) TRACE: Level 50, Segment PER03 (mapping) TRACE: Level 50, Segment PER04 (mapping) TRACE: Level 50, Segment PER05 (mapping empty data) TRACE: Level 50->50, processing Segment PER After Rule- No: 820 TRACE: Performing Rule 506 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 50 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 50 TRACE: Performing Rule 1170 TRACE: Performing Rule 1175 TRACE: Level 50->40, processing Segment def Before Rule- No: 0 TRACE: Level 50->40, processing Segment def After Rule- No: 0 TRACE: Level 40->60, processing Segment NM1 Before Rule- No: 821 TRACE: Level 60, Segment NM1 (mapping) TRACE: Level 60, Segment NM101 (mapping) TRACE: Level 60, Segment NM102 (mapping) TRACE: Level 60, Segment NM103 (mapping) TRACE: Level 60, Segment NM108 (mapping) TRACE: Level 60, Segment NM109 (mapping) TRACE: Level 40->60, processing Segment NM1 After Rule- No: 822 TRACE: Performing Rule 507 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Level 60->40, processing Segment def Before Rule- No: 0 TRACE: Level 60->40, processing Segment def After Rule- No: 0 TRACE: Level 40->70, processing Segment HL Before Rule- No: 9079 TRACE: Level 70, Segment HL (mapping) TRACE: Level 70, Segment HL 01 (mapping) TRACE: Level 70, Segment HL 03 (mapping) TRACE: Level 70, Segment HL 04 (mapping) TRACE: Level 40->70, processing Segment HL After Rule- No: 2000 TRACE: Performing Rule 9079 TRACE: Performing Rule 5035 TRACE: Performing Rule 9079 TRACE: Level 70->70, processing Segment PRV Before Rule- No: 823 TRACE: Level 70, Segment PRV (mapping) TRACE: Level 70, Segment PRV01 (mapping) TRACE: Level 70, Segment PRV02 (mapping) TRACE: Level 70, Segment PRV03 (mapping) TRACE: Level 70->70, processing Segment PRV After Rule- No: 824 TRACE: Performing Rule 510 TRACE: Level 70->80, processing Segment NM1 Before Rule- No: 827 TRACE: Level 80, Segment NM1 (mapping) TRACE: Level 80, Segment NM101 (mapping) TRACE: Level 80, Segment NM102 (mapping) TRACE: Level 80, Segment NM103 (mapping) TRACE: Level 80, Segment NM104 (mapping empty data) TRACE: Level 80, Segment NM105 (mapping empty data) TRACE: Level 80, Segment NM107 (mapping empty data) TRACE: Level 80, Segment NM108 (mapping) TRACE: Level 80, Segment NM109 (mapping) TRACE: Level 70->80, processing Segment NM1 After Rule- No: 828 TRACE: Performing Rule 512 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 1540 TRACE: Performing Rule 22080 TRACE: Level 80, Segment N3 (mapping) TRACE: Level 80, Segment N3 01 (mapping) TRACE: Level 80, Segment N3 02 (mapping empty data) TRACE: Level 80->80, processing Segment N4 Before Rule- No: 829 TRACE: Level 80, Segment N4 (mapping) TRACE: Level 80, Segment N4 01 (mapping) TRACE: Level 80, Segment N4 02 (mapping) TRACE: Level 80, Segment N4 03 (mapping) TRACE: Level 80, Segment N4 03 (mapping) TRACE: Level 80, Segment N4 04 (mapping empty data) TRACE: Level 80->80, processing Segment N4 After Rule- No: 830 TRACE: Performing Rule 515 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 561 TRACE: Performing Rule 10480 TRACE: Performing Rule 10600 TRACE: Performing Rule 10603 TRACE: Rule 10603, Line 2: Start Perform While on Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 13470 TRACE: Level 80->90, processing Segment REF Before Rule- No: 8314 TRACE: Level 90, Segment REF (mapping) TRACE: Level 90, Segment REF01 (mapping) <DISMISSED> Err Lev: 90 Trans: 837 Seg:REF01 REF_16 01Referenc EDI Line: 14 (1297) ERROR: Value <1DXXXXXXXXXXX> is not found in Table- N0160100.XRF TRACE: Level 90, Segment REF01 - Post Edit Rule TRACE: Level 90, Segment REF02 (mapping) TRACE: Level 80->90, processing Segment REF After Rule- No: 832 TRACE: Performing Rule 0 TRACE: Level 90->80, processing Segment def Before Rule- No: 0 TRACE: Level 90->80, processing Segment def After Rule- No: 0 TRACE: Level 80->80, processing Segment PER Before Rule- No: 835 TRACE: Level 80, Segment PER (mapping) TRACE: Level 80, Segment PER01 (mapping) TRACE: Level 80, Segment PER02 (mapping) TRACE: Level 80, Segment PER03 (mapping) TRACE: Level 80, Segment PER04 (mapping) TRACE: Level 80, Segment PER05 (mapping empty data) TRACE: Level 80->80, processing Segment PER After Rule- No: 836 TRACE: Performing Rule 518 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 50 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 50 TRACE: Performing Rule 2135 TRACE: Performing Rule 2138 TRACE: Level 80->70, processing Segment def Before Rule- No: 0 TRACE: Level 80->70, processing Segment def After Rule- No: 0 TRACE: Level 70->120, processing Segment HL Before Rule- No: 2119 TRACE: Performing Rule 2115 TRACE: Performing Rule 5035 TRACE: Performing Rule 5030 TRACE: Performing Rule 9160 TRACE: Level 120, Segment HL (mapping) TRACE: Level 120, Segment HL 01 (mapping) TRACE: Level 120, Segment HL 02 (mapping) TRACE: Level 120, Segment HL 03 (mapping) TRACE: Level 120, Segment HL 04 (mapping) TRACE: Level 70->120, processing Segment HL After Rule- No: 2100 TRACE: Performing Rule 5055 TRACE: Performing Rule 13130 TRACE: Performing Rule 1139 TRACE: Performing Rule 847 TRACE: Level 120->120, processing Segment SBR Before Rule- No: 2002 TRACE: Level 120, Segment SBR (mapping) TRACE: Level 120, Segment SBR01 (mapping) TRACE: Level 120, Segment SBR02 (mapping) TRACE: Level 120, Segment SBR03 (mapping empty data) TRACE: Level 120, Segment SBR04 (mapping empty data) TRACE: Level 120, Segment SBR05 (mapping empty data) TRACE: Level 120, Segment SBR09 (mapping) TRACE: Level 120->120, processing Segment SBR After Rule- No: 2150 TRACE: Performing Rule 2151 TRACE: Performing Rule 2530 TRACE: Performing Rule 2534 TRACE: Level 120->130, processing Segment NM1 Before Rule- No: 845 TRACE: Level 130, Segment NM1 (mapping) TRACE: Level 130, Segment NM101 (mapping) TRACE: Level 130, Segment NM102 (mapping) TRACE: Level 130, Segment NM103 (mapping) TRACE: Level 130, Segment NM104 (mapping) TRACE: Level 130, Segment NM105 (mapping) TRACE: Level 130, Segment NM107 (mapping empty data) TRACE: Level 130, Segment NM108 (mapping) TRACE: Level 130, Segment NM109 (mapping) TRACE: Level 120->130, processing Segment NM1 After Rule- No: 846 TRACE: Performing Rule 528 TRACE: Performing Rule 529 TRACE: Performing Rule 702 TRACE: Performing Rule 705 TRACE: Performing Rule 1200 TRACE: Performing Rule 1205 TRACE: Level 130->130, processing Segment N3 Before Rule- No: 0 TRACE: Level 130, Segment N3 (mapping) TRACE: Level 130, Segment N3 01 (mapping) TRACE: Level 130, Segment N3 02 (mapping) TRACE: Level 130->130, processing Segment N3 After Rule- No: 0 TRACE: Level 130->130, processing Segment N4 Before Rule- No: 847 TRACE: Level 130, Segment N4 (mapping) TRACE: Level 130, Segment N4 01 (mapping) TRACE: Level 130, Segment N4 02 (mapping) TRACE: Level 130, Segment N4 03 (mapping) TRACE: Level 130, Segment N4 03 (mapping) TRACE: Level 130, Segment N4 04 (mapping empty data) TRACE: Level 130->130, processing Segment N4 After Rule- No: 848 TRACE: Performing Rule 530 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 561 TRACE: Performing Rule 10484 TRACE: Performing Rule 10600 TRACE: Performing Rule 10603 TRACE: Rule 10603, Line 2: Start Perform While on Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 13474 TRACE: Level 130->130, processing Segment DMG Before Rule- No: 849 TRACE: Level 130, Segment DMG (mapping) TRACE: Level 130, Segment DMG01 (mapping) TRACE: Level 130, Segment DMG02 (mapping) TRACE: Level 130, Segment DMG03 (mapping) TRACE: Level 130->130, processing Segment DMG After Rule- No: 850 TRACE: Performing Rule 531 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Level 130->120, processing Segment def Before Rule- No: 0 TRACE: Level 130->120, processing Segment def After Rule- No: 0 TRACE: Level 120->160, processing Segment NM1 Before Rule- No: 855 TRACE: Performing Rule 2164 TRACE: Performing Rule 2165 TRACE: Level 160, Segment NM1 (mapping) TRACE: Level 160, Segment NM101 (mapping) TRACE: Level 160, Segment NM102 (mapping) TRACE: Level 160, Segment NM103 (mapping) TRACE: Level 160, Segment NM108 (mapping) TRACE: Level 160, Segment NM109 (mapping) TRACE: Level 120->160, processing Segment NM1 After Rule- No: 856 TRACE: Performing Rule 534 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Level 160->120, processing Segment def Before Rule- No: 0 TRACE: Level 160->120, processing Segment def After Rule- No: 0 TRACE: Level 120->230, processing Segment CLM Before Rule- No: 881 TRACE: Performing Rule 555 TRACE: Performing Rule 919 TRACE: Performing Rule 2190 TRACE: Performing Rule 9160 TRACE: Performing Rule 13500 TRACE: Level 230, Segment CLM (mapping) TRACE: Level 230, Segment CLM01 (mapping) TRACE: Level 230, Segment CLM02 (mapping) TRACE: Level 230, Segment CLM02 - Post Edit Rule TRACE: Performing Rule 10250 TRACE: Performing Rule 10251 TRACE: Level 230, Segment CLM0501 (mapping) TRACE: Level 230, Segment CLM0503 (mapping) TRACE: Level 230, Segment CLM06 (mapping) TRACE: Level 230, Segment CLM07 (mapping) TRACE: Level 230, Segment CLM08 (mapping) TRACE: Level 230, Segment CLM09 (mapping) TRACE: Level 230, Segment CLM10 (mapping) TRACE: Level 230, Segment CLM1101 (mapping empty data) TRACE: Level 120->230, processing Segment CLM After Rule- No: 882 TRACE: Performing Rule 555 TRACE: Performing Rule 2300 TRACE: Performing Rule 2302 TRACE: Performing Rule 2303 TRACE: Performing Rule 9990 TRACE: Performing Rule 800 TRACE: Performing Rule 2230 TRACE: Performing Rule 13520 TRACE: Level 230, Segment NTE (mapping) TRACE: Level 230, Segment NTE01 (mapping) TRACE: Level 230, Segment NTE02 (mapping) TRACE: Level 230->230, processing Segment CR1 Before Rule- No: 915 TRACE: Level 230, Segment CR1 (mapping) TRACE: Level 230, Segment CR101 (mapping empty data) TRACE: Level 230, Segment CR102 (mapping empty data) TRACE: Level 230, Segment CR103 (mapping) TRACE: Level 230, Segment CR104 (mapping) TRACE: Level 230, Segment CR105 (mapping) TRACE: Level 230, Segment CR106 (mapping) TRACE: Level 230, Segment CR109 (mapping) TRACE: Level 230, Segment CR110 (mapping empty data) TRACE: Level 230->230, processing Segment CR1 After Rule- No: 916 TRACE: Performing Rule 597 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 50 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 2460 TRACE: Level 230->610, processing Segment CRC Before Rule- No: 0 TRACE: Level 610, Segment CRC (mapping) TRACE: Level 610, Segment CRC01 (mapping) TRACE: Level 610, Segment CRC02 (mapping) TRACE: Level 610, Segment CRC03 (mapping) TRACE: Level 610, Segment CRC04 (mapping empty data) TRACE: Level 230->610, processing Segment CRC After Rule- No: 2313 TRACE: Level 610->230, processing Segment def Before Rule- No: 0 TRACE: Level 610->230, processing Segment def After Rule- No: 0 TRACE: Level 230->710, processing Segment NM1 Before Rule- No: 9411 TRACE: Level 710, Segment NM1 (mapping) TRACE: Level 710, Segment NM101 (mapping) TRACE: Level 710, Segment NM102 (mapping) TRACE: Level 710, Segment NM103 (mapping) TRACE: Level 230->710, processing Segment NM1 After Rule- No: 942 TRACE: Performing Rule 622 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 50 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 9480 TRACE: Performing Rule 4058 TRACE: Performing Rule 22080 TRACE: Level 710, Segment N3 (mapping) TRACE: Level 710, Segment N3 01 (mapping) TRACE: Level 710, Segment N3 02 (mapping empty data) TRACE: Level 710->710, processing Segment N4 Before Rule- No: 943 TRACE: Level 710, Segment N4 (mapping) TRACE: Level 710, Segment N4 01 (mapping) TRACE: Level 710, Segment N4 02 (mapping) TRACE: Level 710, Segment N4 03 (mapping) TRACE: Level 710, Segment N4 03 (mapping) TRACE: Level 710, Segment N4 04 (mapping empty data) TRACE: Level 710->710, processing Segment N4 After Rule- No: 944 TRACE: Performing Rule 561 TRACE: Performing Rule 10492 TRACE: Performing Rule 10600 TRACE: Performing Rule 10603 TRACE: Rule 10603, Line 2: Start Perform While on Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 13482 TRACE: Level 710->230, processing Segment def Before Rule- No: 0 TRACE: Level 710->230, processing Segment def After Rule- No: 0 TRACE: Level 230->760, processing Segment SBR Before Rule- No: 10000 TRACE: Level 760, Segment SBR (mapping) TRACE: Level 760, Segment SBR01 (mapping) TRACE: Level 760, Segment SBR02 (mapping) TRACE: Level 760, Segment SBR03 (mapping empty data) TRACE: Level 760, Segment SBR04 (mapping empty data) TRACE: Level 760, Segment SBR05 (mapping) TRACE: Level 760, Segment SBR09 (mapping) TRACE: Level 230->760, processing Segment SBR After Rule- No: 0 TRACE: Level 760->760, processing Segment DMG Before Rule- No: 971 TRACE: Level 760, Segment DMG (mapping) TRACE: Level 760, Segment DMG01 (mapping) TRACE: Level 760, Segment DMG02 (mapping) TRACE: Level 760, Segment DMG03 (mapping) TRACE: Level 760->760, processing Segment DMG After Rule- No: 972 TRACE: Performing Rule 657 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Level 760->760, processing Segment OI Before Rule- No: 0 TRACE: Level 760, Segment OI (mapping) TRACE: Level 760, Segment OI 03 (mapping) TRACE: Level 760, Segment OI 04 (mapping) TRACE: Level 760, Segment OI 06 (mapping) TRACE: Level 760->760, processing Segment OI After Rule- No: 2398 TRACE: Performing Rule 2399 TRACE: Level 760->870, processing Segment NM1 Before Rule- No: 973 TRACE: Level 870, Segment NM1 (mapping) TRACE: Level 870, Segment NM101 (mapping) TRACE: Level 870, Segment NM102 (mapping) TRACE: Level 870, Segment NM103 (mapping) TRACE: Level 870, Segment NM104 (mapping) TRACE: Level 870, Segment NM105 (mapping) TRACE: Level 870, Segment NM107 (mapping empty data) TRACE: Level 870, Segment NM108 (mapping) TRACE: Level 870, Segment NM109 (mapping) TRACE: Level 760->870, processing Segment NM1 After Rule- No: 974 TRACE: Performing Rule 660 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 2361 TRACE: Performing Rule 4082 TRACE: Level 870->760, processing Segment def Before Rule- No: 0 TRACE: Level 870->760, processing Segment def After Rule- No: 0 TRACE: Level 760->880, processing Segment NM1 Before Rule- No: 979 TRACE: Level 880, Segment NM1 (mapping) TRACE: Level 880, Segment NM101 (mapping) TRACE: Level 880, Segment NM102 (mapping) TRACE: Level 880, Segment NM103 (mapping) TRACE: Level 880, Segment NM108 (mapping) TRACE: Level 880, Segment NM109 (mapping) TRACE: Level 760->880, processing Segment NM1 After Rule- No: 980 TRACE: Performing Rule 665 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 4083 TRACE: Level 880->760, processing Segment def Before Rule- No: 0 TRACE: Level 880->760, processing Segment def After Rule- No: 0 TRACE: Level 760->230, processing Segment def Before Rule- No: 0 TRACE: Level 760->230, processing Segment def After Rule- No: 0 TRACE: Level 230->1020, processing Segment LX Before Rule- No: 2400 TRACE: Performing Rule 0 TRACE: Performing Rule 13140 TRACE: Performing Rule 13145 TRACE: Performing Rule 9045 TRACE: Performing Rule 9048 TRACE: Performing Rule 0 TRACE: Performing Rule 2335 TRACE: Performing Rule 2336 TRACE: Performing Rule 2230 TRACE: Performing Rule 1245 TRACE: Performing Rule 1268 TRACE: Performing Rule 2190 TRACE: Level 1020, Segment LX (mapping) TRACE: Level 1020, Segment LX 01 (mapping) TRACE: Level 230->1020, processing Segment LX After Rule- No: 2410 TRACE: Performing Rule 2560 TRACE: Performing Rule 10010 TRACE: Performing Rule 7201 TRACE: Level 1020->1020, processing Segment SV1 Before Rule- No: 1029 TRACE: Level 1020, Segment SV1 (mapping) TRACE: Level 1020, Segment SV10101 (mapping) TRACE: Level 1020, Segment SV10102 (mapping) TRACE: Level 1020, Segment SV10103 (mapping empty data) TRACE: Level 1020, Segment SV10104 (mapping empty data) TRACE: Level 1020, Segment SV10105 (mapping empty data) TRACE: Level 1020, Segment SV10106 (mapping empty data) TRACE: Level 1020, Segment SV102 (mapping) TRACE: Level 1020, Segment SV102 - Post Edit Rule TRACE: Performing Rule 10250 TRACE: Performing Rule 10251 TRACE: Level 1020, Segment SV103 (mapping) TRACE: Level 1020, Segment SV104 (mapping) TRACE: Level 1020, Segment SV105 (mapping empty data) TRACE: Level 1020, Segment SV10701 (mapping empty data) TRACE: Level 1020, Segment SV10702 (mapping empty data) TRACE: Level 1020, Segment SV10703 (mapping empty data) TRACE: Level 1020, Segment SV10704 (mapping empty data) TRACE: Level 1020, Segment SV109 (mapping empty data) TRACE: Level 1020, Segment SV111 (mapping empty data) TRACE: Level 1020, Segment SV112 (mapping empty data) TRACE: Level 1020, Segment SV115 (mapping) TRACE: Level 1020->1020, processing Segment SV1 After Rule- No: 1030 TRACE: Performing Rule 693 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 2185 TRACE: Performing Rule 9150 TRACE: Performing Rule 9154 TRACE: Performing Rule 9154 TRACE: Performing Rule 9154 TRACE: Performing Rule 9154 TRACE: Level 1020->1070, processing Segment DTP Before Rule- No: 0 TRACE: Level 1070, Segment DTP (mapping) TRACE: Level 1070, Segment DTP01 (mapping) TRACE: Level 1070, Segment DTP02 (mapping) TRACE: Level 1070, Segment DTP03 (mapping) TRACE: Level 1070, Segment DTP03 - Post Edit Rule TRACE: Level 1020->1070, processing Segment DTP After Rule- No: 2448 TRACE: Performing Rule 2449 TRACE: Performing Rule 2540 TRACE: Performing Rule 4116 TRACE: Performing Rule 4117 TRACE: Performing Rule 2454 TRACE: Performing Rule 2417 TRACE: Performing Rule 2418 TRACE: Level 1070->1020, processing Segment def Before Rule- No: 0 TRACE: Level 1070->1020, processing Segment def After Rule- No: 0 TRACE: Level 1020->1290, processing Segment REF Before Rule- No: 1053 TRACE: Level 1290, Segment REF (mapping) TRACE: Level 1290, Segment REF01 (mapping) TRACE: Level 1290, Segment REF02 (mapping) TRACE: Level 1020->1290, processing Segment REF After Rule- No: 1054 TRACE: Performing Rule 4154 TRACE: Level 1290->1020, processing Segment def Before Rule- No: 0 TRACE: Level 1290->1020, processing Segment def After Rule- No: 0 TRACE: Level 1020->1520, processing Segment SVD Before Rule- No: 0 TRACE: Level 1520, Segment SVD (mapping) TRACE: Level 1520, Segment SVD01 (mapping) TRACE: Level 1520, Segment SVD01 - Post Edit Rule TRACE: Level 1520, Segment SVD02 (mapping) TRACE: Level 1520, Segment SVD02 - Post Edit Rule TRACE: Performing Rule 10250 TRACE: Performing Rule 10251 TRACE: Level 1520, Segment SVD0301 (mapping) TRACE: Level 1520, Segment SVD0301 - Post Edit Rule TRACE: Performing Rule 13245 TRACE: Level 1520, Segment SVD0302 (mapping) TRACE: Level 1520, Segment SVD0303 (mapping empty data) TRACE: Level 1520, Segment SVD0304 (mapping empty data) TRACE: Level 1520, Segment SVD0305 (mapping empty data) TRACE: Level 1520, Segment SVD0306 (mapping empty data) TRACE: Level 1520, Segment SVD0307 (mapping empty data) TRACE: Level 1520, Segment SVD05 (mapping) TRACE: Level 1520, Segment SVD06 (mapping empty data) TRACE: Level 1020->1520, processing Segment SVD After Rule- No: 0 TRACE: Level 1520->1520, processing Segment CAS Before Rule- No: 1131 TRACE: Level 1520, Segment CAS (mapping) TRACE: Level 1520, Segment CAS01 (mapping) TRACE: Level 1520, Segment CAS02 (mapping) TRACE: Level 1520, Segment CAS03 (mapping) TRACE: Level 1520, Segment CAS03 - Post Edit Rule TRACE: Performing Rule 10250 TRACE: Performing Rule 10251 TRACE: Level 1520, Segment CAS04 (mapping empty data) TRACE: Level 1520->1520, processing Segment CAS After Rule- No: 1132 TRACE: Performing Rule 792 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 3 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 3 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 3 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 3 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 3 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Level 1520->1520, processing Segment DTP Before Rule- No: 0 TRACE: Level 1520, Segment DTP (mapping) TRACE: Level 1520, Segment DTP01 (mapping) TRACE: Level 1520, Segment DTP01 - Post Edit Rule TRACE: Performing Rule 10465 TRACE: Level 1520, Segment DTP02 (mapping) TRACE: Level 1520, Segment DTP03 (mapping) TRACE: Level 1520->1520, processing Segment DTP After Rule- No: 0 TRACE: Level 1520->1020, processing Segment def Before Rule- No: 0 TRACE: Level 1520->1020, processing Segment def After Rule- No: 0 TRACE: Level 1020->120, processing Segment HL Before Rule- No: 2119 TRACE: Performing Rule 9080 TRACE: Performing Rule 2010 TRACE: Performing Rule 2105 TRACE: Performing Rule 2115 TRACE: Performing Rule 5035 TRACE: Performing Rule 5030 TRACE: Performing Rule 9160 TRACE: Level 120, Segment HL (mapping) TRACE: Level 120, Segment HL 01 (mapping) TRACE: Level 120, Segment HL 02 (mapping) TRACE: Level 120, Segment HL 03 (mapping) TRACE: Level 120, Segment HL 04 (mapping) TRACE: Level 1020->120, processing Segment HL After Rule- No: 2100 TRACE: Performing Rule 5055 TRACE: Performing Rule 13130 TRACE: Performing Rule 1139 TRACE: Performing Rule 847 TRACE: Level 120->120, processing Segment SBR Before Rule- No: 2002 TRACE: Level 120, Segment SBR (mapping) TRACE: Level 120, Segment SBR01 (mapping) TRACE: Level 120, Segment SBR02 (mapping) TRACE: Level 120, Segment SBR03 (mapping empty data) TRACE: Level 120, Segment SBR04 (mapping empty data) TRACE: Level 120, Segment SBR05 (mapping empty data) TRACE: Level 120, Segment SBR09 (mapping) TRACE: Level 120->120, processing Segment SBR After Rule- No: 2150 TRACE: Performing Rule 2151 TRACE: Performing Rule 2530 TRACE: Performing Rule 2534 TRACE: Level 120->130, processing Segment NM1 Before Rule- No: 845 TRACE: Level 130, Segment NM1 (mapping) TRACE: Level 130, Segment NM101 (mapping) TRACE: Level 130, Segment NM102 (mapping) TRACE: Level 130, Segment NM103 (mapping) TRACE: Level 130, Segment NM104 (mapping) TRACE: Level 130, Segment NM105 (mapping) TRACE: Level 130, Segment NM107 (mapping empty data) TRACE: Level 130, Segment NM108 (mapping) TRACE: Level 130, Segment NM109 (mapping) TRACE: Level 120->130, processing Segment NM1 After Rule- No: 846 TRACE: Performing Rule 528 TRACE: Performing Rule 529 TRACE: Performing Rule 702 TRACE: Performing Rule 705 TRACE: Performing Rule 1200 TRACE: Performing Rule 1205 TRACE: Level 130->130, processing Segment N3 Before Rule- No: 0 TRACE: Level 130, Segment N3 (mapping) TRACE: Level 130, Segment N3 01 (mapping) TRACE: Level 130, Segment N3 02 (mapping) TRACE: Level 130->130, processing Segment N3 After Rule- No: 0 TRACE: Level 130->130, processing Segment N4 Before Rule- No: 847 TRACE: Level 130, Segment N4 (mapping) TRACE: Level 130, Segment N4 01 (mapping) TRACE: Level 130, Segment N4 02 (mapping) TRACE: Level 130, Segment N4 03 (mapping) TRACE: Level 130, Segment N4 03 (mapping) TRACE: Level 130, Segment N4 04 (mapping empty data) TRACE: Level 130->130, processing Segment N4 After Rule- No: 848 TRACE: Performing Rule 530 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 561 TRACE: Performing Rule 10484 TRACE: Performing Rule 10600 TRACE: Performing Rule 10603 TRACE: Rule 10603, Line 2: Start Perform While on Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 13474 TRACE: Level 130->130, processing Segment DMG Before Rule- No: 849 TRACE: Level 130, Segment DMG (mapping) TRACE: Level 130, Segment DMG01 (mapping) TRACE: Level 130, Segment DMG02 (mapping) TRACE: Level 130, Segment DMG03 (mapping) TRACE: Level 130->130, processing Segment DMG After Rule- No: 850 TRACE: Performing Rule 531 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Level 130->120, processing Segment def Before Rule- No: 0 TRACE: Level 130->120, processing Segment def After Rule- No: 0 TRACE: Level 120->160, processing Segment NM1 Before Rule- No: 855 TRACE: Performing Rule 2164 TRACE: Performing Rule 2165 TRACE: Level 160, Segment NM1 (mapping) TRACE: Level 160, Segment NM101 (mapping) TRACE: Level 160, Segment NM102 (mapping) TRACE: Level 160, Segment NM103 (mapping) TRACE: Level 160, Segment NM108 (mapping) TRACE: Level 160, Segment NM109 (mapping) TRACE: Level 120->160, processing Segment NM1 After Rule- No: 856 TRACE: Performing Rule 534 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Level 160->120, processing Segment def Before Rule- No: 0 TRACE: Level 160->120, processing Segment def After Rule- No: 0 TRACE: Level 120->230, processing Segment CLM Before Rule- No: 881 TRACE: Performing Rule 555 TRACE: Performing Rule 919 TRACE: Performing Rule 2190 TRACE: Performing Rule 9160 TRACE: Performing Rule 13500 TRACE: Level 230, Segment CLM (mapping) TRACE: Level 230, Segment CLM01 (mapping) TRACE: Level 230, Segment CLM02 (mapping) TRACE: Level 230, Segment CLM02 - Post Edit Rule TRACE: Performing Rule 10250 TRACE: Performing Rule 10251 TRACE: Level 230, Segment CLM0501 (mapping) TRACE: Level 230, Segment CLM0503 (mapping) TRACE: Level 230, Segment CLM06 (mapping) TRACE: Level 230, Segment CLM07 (mapping) TRACE: Level 230, Segment CLM08 (mapping) TRACE: Level 230, Segment CLM09 (mapping) TRACE: Level 230, Segment CLM10 (mapping) TRACE: Level 230, Segment CLM1101 (mapping empty data) TRACE: Level 120->230, processing Segment CLM After Rule- No: 882 TRACE: Performing Rule 555 TRACE: Performing Rule 2300 TRACE: Performing Rule 2302 TRACE: Performing Rule 2303 TRACE: Performing Rule 9990 TRACE: Performing Rule 800 TRACE: Performing Rule 2230 TRACE: Performing Rule 13520 TRACE: Level 230, Segment NTE (mapping) TRACE: Level 230, Segment NTE01 (mapping) TRACE: Level 230, Segment NTE02 (mapping) TRACE: Level 230->230, processing Segment CR1 Before Rule- No: 915 TRACE: Level 230, Segment CR1 (mapping) TRACE: Level 230, Segment CR101 (mapping empty data) TRACE: Level 230, Segment CR102 (mapping empty data) TRACE: Level 230, Segment CR103 (mapping) TRACE: Level 230, Segment CR104 (mapping) TRACE: Level 230, Segment CR105 (mapping) TRACE: Level 230, Segment CR106 (mapping) TRACE: Level 230, Segment CR109 (mapping) TRACE: Level 230, Segment CR110 (mapping empty data) TRACE: Level 230->230, processing Segment CR1 After Rule- No: 916 TRACE: Performing Rule 597 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 50 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 2460 TRACE: Level 230->610, processing Segment CRC Before Rule- No: 0 TRACE: Level 610, Segment CRC (mapping) TRACE: Level 610, Segment CRC01 (mapping) TRACE: Level 610, Segment CRC02 (mapping) TRACE: Level 610, Segment CRC03 (mapping) TRACE: Level 610, Segment CRC04 (mapping empty data) TRACE: Level 230->610, processing Segment CRC After Rule- No: 2313 TRACE: Level 610->230, processing Segment def Before Rule- No: 0 TRACE: Level 610->230, processing Segment def After Rule- No: 0 TRACE: Level 230->710, processing Segment NM1 Before Rule- No: 9411 TRACE: Level 710, Segment NM1 (mapping) TRACE: Level 710, Segment NM101 (mapping) TRACE: Level 710, Segment NM102 (mapping) TRACE: Level 710, Segment NM103 (mapping) TRACE: Level 230->710, processing Segment NM1 After Rule- No: 942 TRACE: Performing Rule 622 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 50 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 9480 TRACE: Performing Rule 4058 TRACE: Performing Rule 22080 TRACE: Level 710, Segment N3 (mapping) TRACE: Level 710, Segment N3 01 (mapping) TRACE: Level 710, Segment N3 02 (mapping empty data) TRACE: Level 710->710, processing Segment N4 Before Rule- No: 943 TRACE: Level 710, Segment N4 (mapping) TRACE: Level 710, Segment N4 01 (mapping) TRACE: Level 710, Segment N4 02 (mapping) TRACE: Level 710, Segment N4 03 (mapping) TRACE: Level 710, Segment N4 03 (mapping) TRACE: Level 710, Segment N4 04 (mapping empty data) TRACE: Level 710->710, processing Segment N4 After Rule- No: 944 TRACE: Performing Rule 561 TRACE: Performing Rule 10492 TRACE: Performing Rule 10600 TRACE: Performing Rule 10603 TRACE: Rule 10603, Line 2: Start Perform While on Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 10605 TRACE: Performing Rule 13482 TRACE: Level 710->230, processing Segment def Before Rule- No: 0 TRACE: Level 710->230, processing Segment def After Rule- No: 0 TRACE: Level 230->760, processing Segment SBR Before Rule- No: 10000 TRACE: Level 760, Segment SBR (mapping) TRACE: Level 760, Segment SBR01 (mapping) TRACE: Level 760, Segment SBR02 (mapping) TRACE: Level 760, Segment SBR03 (mapping empty data) TRACE: Level 760, Segment SBR04 (mapping empty data) TRACE: Level 760, Segment SBR05 (mapping) TRACE: Level 760, Segment SBR09 (mapping) TRACE: Level 230->760, processing Segment SBR After Rule- No: 0 TRACE: Level 760->760, processing Segment DMG Before Rule- No: 971 TRACE: Level 760, Segment DMG (mapping) TRACE: Level 760, Segment DMG01 (mapping) TRACE: Level 760, Segment DMG02 (mapping) TRACE: Level 760, Segment DMG03 (mapping) TRACE: Level 760->760, processing Segment DMG After Rule- No: 972 TRACE: Performing Rule 657 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Level 760->760, processing Segment OI Before Rule- No: 0 TRACE: Level 760, Segment OI (mapping) TRACE: Level 760, Segment OI 03 (mapping) TRACE: Level 760, Segment OI 04 (mapping) TRACE: Level 760, Segment OI 06 (mapping) TRACE: Level 760->760, processing Segment OI After Rule- No: 2398 TRACE: Performing Rule 2399 TRACE: Level 760->870, processing Segment NM1 Before Rule- No: 973 TRACE: Level 870, Segment NM1 (mapping) TRACE: Level 870, Segment NM101 (mapping) TRACE: Level 870, Segment NM102 (mapping) TRACE: Level 870, Segment NM103 (mapping) TRACE: Level 870, Segment NM104 (mapping) TRACE: Level 870, Segment NM105 (mapping) TRACE: Level 870, Segment NM107 (mapping empty data) TRACE: Level 870, Segment NM108 (mapping) TRACE: Level 870, Segment NM109 (mapping) TRACE: Level 760->870, processing Segment NM1 After Rule- No: 974 TRACE: Performing Rule 660 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 2361 TRACE: Performing Rule 4082 TRACE: Level 870->760, processing Segment def Before Rule- No: 0 TRACE: Level 870->760, processing Segment def After Rule- No: 0 TRACE: Level 760->880, processing Segment NM1 Before Rule- No: 979 TRACE: Level 880, Segment NM1 (mapping) TRACE: Level 880, Segment NM101 (mapping) TRACE: Level 880, Segment NM102 (mapping) TRACE: Level 880, Segment NM103 (mapping) TRACE: Level 880, Segment NM108 (mapping) TRACE: Level 880, Segment NM109 (mapping) TRACE: Level 760->880, processing Segment NM1 After Rule- No: 980 TRACE: Performing Rule 665 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 2 TRACE: Performing Rule 60 TRACE: Performing Rule 4083 TRACE: Level 880->760, processing Segment def Before Rule- No: 0 TRACE: Level 880->760, processing Segment def After Rule- No: 0 TRACE: Level 760->230, processing Segment def Before Rule- No: 0 TRACE: Level 760->230, processing Segment def After Rule- No: 0 TRACE: Level 230->1020, processing Segment LX Before Rule- No: 2400 TRACE: Performing Rule 0 TRACE: Performing Rule 13140 TRACE: Performing Rule 13145 TRACE: Performing Rule 9045 TRACE: Performing Rule 9048 TRACE: Performing Rule 0 TRACE: Performing Rule 2335 TRACE: Performing Rule 2336 TRACE: Performing Rule 2230 TRACE: Performing Rule 1245 TRACE: Performing Rule 1268 TRACE: Performing Rule 2190 TRACE: Level 1020, Segment LX (mapping) TRACE: Level 1020, Segment LX 01 (mapping) TRACE: Level 230->1020, processing Segment LX After Rule- No: 2410 TRACE: Performing Rule 2560 TRACE: Performing Rule 10010 TRACE: Performing Rule 7201 TRACE: Level 1020->1020, processing Segment SV1 Before Rule- No: 1029 TRACE: Level 1020, Segment SV1 (mapping) TRACE: Level 1020, Segment SV10101 (mapping) TRACE: Level 1020, Segment SV10102 (mapping) TRACE: Level 1020, Segment SV10103 (mapping empty data) TRACE: Level 1020, Segment SV10104 (mapping empty data) TRACE: Level 1020, Segment SV10105 (mapping empty data) TRACE: Level 1020, Segment SV10106 (mapping empty data) TRACE: Level 1020, Segment SV102 (mapping) TRACE: Level 1020, Segment SV102 - Post Edit Rule TRACE: Performing Rule 10250 TRACE: Performing Rule 10251 TRACE: Level 1020, Segment SV103 (mapping) TRACE: Level 1020, Segment SV104 (mapping) TRACE: Level 1020, Segment SV105 (mapping empty data) TRACE: Level 1020, Segment SV10701 (mapping empty data) TRACE: Level 1020->1020, processing Segment SV1 After Rule- No: 1030 TRACE: Performing Rule 693 TRACE: Performing Rule 10 TRACE: Performing Rule 1 TRACE: Performing Rule 20 TRACE: Performing Rule 2 TRACE: Performing Rule 20 TRACE: Performing Rule 2185 TRACE: Performing Rule 9150 TRACE: Performing Rule 9154 TRACE: Performing Rule 9154 TRACE: Performing Rule 9154 TRACE: Performing Rule 9154 TRACE: Level 1020->1070, processing Segment DTP Before Rule- No: 0 TRACE: Level 1070, Segment DTP (mapping) TRACE: Level 1070, Segment DTP01 (mapping) TRACE: Level 1070, Segment DTP02 (mapping) TRACE: Level 1070, Segment DTP03 (mapping) TRACE: Level 1070, Segment DTP03 - Post Edit Rule TRACE: Level 1020->1070, processing Segment DTP After Rule- No: 2448 TRACE: Performing Rule 2449 TRACE: Performing Rule 2540 TRACE: Performing Rule 4116 TRACE: Performing Rule 4117 TRACE: Performing Rule 2454 TRACE: Performing Rule 2417 TRACE: Performing Rule 2418 TRACE: Level 1070->1020, processing Segment def Before Rule- No: 0 TRACE: Level 1070->1020, processing Segment def After Rule- No: 0 TRACE: Level 1020->1290, processing Segment REF Before Rule- No: 1053 TRACE: Level 1290, Segment REF (mapping) TRACE: Level 1290, Segment REF01 (mapping) TRACE: Level 1290, Segment REF02 (mapping) TRACE: Level 1020->1290, processing Segment REF After Rule- No: 1054 TRACE: Performing Rule 4154 TRACE: Level 1290->1020, processing Segment def Before Rule- No: 0 TRACE: Level 1290->1020, processing Segment def After Rule- No: 0 TRACE: Level 1020->1520, processing Segment SVD Before Rule- No: 0 TRACE: Level 1520, Segment SVD (mapping) TRACE: Level 1520, Segment SVD01 (mapping) TRACE: Level 1520, Segment SVD01 - Post Edit Rule TRACE: Level 1520, Segment SVD02 (mapping) TRACE: Level 1520, Segment SVD02 - Post Edit Rule TRACE: Performing Rule 10250 TRACE: Performing Rule 10251 TRACE: Level 1520, Segment SVD0301 (mapping) TRACE: Level 1520, Segment SVD0301 - Post Edit Rule TRACE: Performing Rule 13245 TRACE: Level 1520, Segment SVD0302 (mapping) TRACE: Level 1520, Segment SVD0303 (mapping empty data) TRACE: Level 1520, Segment SVD0304 (mapping empty data) TRACE: Level 1520, Segment SVD0305 (mapping empty data) TRACE: Level 1520, Segment SVD0306 (mapping empty data) TRACE: Level 1520, Segment SVD0307 (mapping empty data) TRACE: Level 1520, Segment SVD05 (mapping) TRACE: Level 1520, Segment SVD06 (mapping empty data) TRACE: Level 1020->1520, processing Segment SVD After Rule- No: 0 TRACE: Level CR:624808 CR Number:   624808 Product Name:   PB Enterprise Product Component:   PB Web Services Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Open a web service proxy or create a new proxy causes pb 12 dlls to get loaded in memory. The dlls that get loaded are: pbshr12.dll pbwsdlclient12.dll pbcsi12.dll CR:624823 CR Number:   624823 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Open OS:   Microsoft Windows 2003 Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Customer sent in crash dump of crash they have not been able to replicate in a testcase. Requesting analysis of crash dump. Faulting in MS dlls on initial analysis MODULE_NAME: MSVCR71 FAULTING_MODULE: 7c800000 ntdll CR:624975 CR Number:   624975 Product Name:   PB Enterprise Product Component:   MAPI Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Jul 2010 Fixed Description Customer is migrating an application from PB 9 to PB 11.5.1. Throughout their code there are places where they send null as the message in an email. In PB 9 this works but in PB 11.5.1 this fails. They know that if they set the message to an empty string the mail is successfully sent but as they have the code to set it to null throughout their code they would like it to work as it did in PB 9. CR:624978 CR Number:   624978 Product Name:   PB Enterprise Product Component:   Rich Text Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0 08 Jun 2010 Fixed Description A SaveDocument to html does not preserve the hyperlink in a rte control. rte_1.SaveDocument("myhtml.htm", FileTypeHTML!) CR:625151 CR Number:   625151 Product Name:   PB Enterprise Product Component:   PB.NET WebForm Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Apr 2010 Fixed 26 Apr 2010 Fixed Description The date-picker gets truncated together with tab control inside userobject. Seems related to CR 480110. CR:625152 CR Number:   625152 Product Name:   PB Enterprise Product Component:   ORCA Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description The customer is doing some complex deployment automation using PB11.5 and ORCAScript. They have multiple projects run in multiple passes and *most* of them work. They have a couple that fail, and when they fail, all that is reported is "-20". This is basically meaningless. They're using "Build Project with overrides" and the projects all work within the PB IDE, and the information they're feeding to ORCAScript matches up as far as they can see. Is there some way to get ORCASCript to be more verbose about what it is failing on and what it is expecting? CR:625164 CR Number:   625164 Product Name:   PB Enterprise Product Component:   Shared Objects Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 Apr 2010 Presently Not Targeted For Any Future Release Of This Product Description Customer's multi-threaded application is now hanging on dual processor machines. This is a continuation of CR 612444 which was crashing. It seems as though it is hanging when the thread count reaches over 40. CR:625276 CR Number:   625276 Product Name:   PB Enterprise Product Component:   DW Display Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.5 25 Apr 2010 Fixed Description Refresh problem when changing DW band color using an expression. Workaround Description  In the itemChanged event put this code : if dwo.name = column_name THEN dw_1.post setredraw (true) CR:625300 CR Number:   625300 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 21 Apr 2010 Fixed Description ImportString call causes crash when imported string is large Used syntax: li_ret = lds_dest.ImportString(dw_2.Object.DataWindow.Data) CR:625304 CR Number:   625304 Product Name:   PB Enterprise Product Component:   SYSAM Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description The current implementation of served PB licenses is confusing for the administrator of the SySAM server. The server will keep track of the number of checked out PB licenses, but after a restart of the server, it reports zero licenses in use, even though any number could be in use. CR:625307 CR Number:   625307 Product Name:   PB Enterprise Product Component:   DW Display Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 Apr 2010 Fixed Description Column Background.Color 'Transparent' shows DataWindow background color. CR:625310 CR Number:   625310 Product Name:   PB Enterprise Product Component:   Script Painter Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description In a script painter of an object, when the first function has more than 40 arguments then the dropdown function list always shows this first function. When editing a different function the dropdown list cannot be used to select the first function. CR:625318 CR Number:   625318 Product Name:   PB Enterprise Product Component:   DW Expression Status:   Closed OS:   Windows XP Original Version:   11.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 May 2010 Fixed Description Group DataWindow with computed expression: sum(<if_column_expression> for group 1 distinct <column>) PowerBuilder crashed when trying to edit the expression without using the button "..." if the preview has rows loaded The result of the sum expression was incorrect although the equivalent count expression looked correct. CR:625337 CR Number:   625337 Product Name:   PB Enterprise Product Component:   DB Sybase System Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Apr 2010 Fixed Description OS: Windows XP SP3 Versions and Build #s Tested: PB 11.5.1_4716 and 11.5.1_4726 Database/Driver File/Version: SYC connecting to: Adaptive Server Enterprise/15.0.3/EBF 16747 Cluster Edition/P/Sun_svr4/OS 5.8/asepyxis/2837/64-bit/FBO/Mon Jun 1 10:18:57 2009 In PB Machine, using Sybase CTISQL Utility/15.5/P-EBF17655 ESD #3/PC Intel/BUILD1550-005/OPT/Thu Feb 18 01:47:22 2010 Comments: DBPARM DelimitIdentifier='Yes' causes syntax error in SQL SELECT at the moment failover occurs in ASE Cluster Edition. If dropping such DBPARM, Failover occurs correctly. Workaround Description  By setting DelimitIdentifier='No' works fine, but customer is migrating existing applications that depend on 'Yes' for this DBPARM. CR:625471 CR Number:   625471 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Apr 2010 Fixed Description PB will crash in the pbshr when calling the following datawindow dot notation: dw_1.object.data.selected = dw_2.object.data Workaround Description  long ll_row ll_row = dw_1.getselectedrow(0) dw_1.deleterow(ll_row) dw_2.rowscopy(dw_2.getrow(),dw_2.rowcount(),primary!,dw_1,ll_row,Primary!) CR:625623 CR Number:   625623 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 May 2010 Fixed Description When tabbing out of a htmldw protected column with a display format of [currency], the following error results: Item 'xxxxx' does not pass validation test CR:625624 CR Number:   625624 Product Name:   PB Enterprise Product Component:   DW Printing Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 May 2010 Fixed Description Customer has a composite report with several datawindows. One datawindow itself has two nested reports. In all versions, the online display of the report has the correct page numbers. When saved to a PDF report and printed, the PB 9 report has the correct page numbers but when migrated to PB 11.5.1 the two last pages both report page 2 of 2. CR:625748 CR Number:   625748 Product Name:   PB Enterprise Product Component:   Window Painter Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description When opening windows and userobjects in libraries that are situated on a network drive the opening and saving of these objects takes a long time. (ie. > 30 or 45sec.). In PB 6.5 the times were considerably faster then PB 11.5. CR:625774 CR Number:   625774 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   Linux Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Apr 2010 Workaround Description Powerbuilder OS: Windows XP SP3 Versions and Build #s Tested: - Powerbuilder 11.5.1_4608 - PBVM 11.5.1_4608 on EAServer 6.3.0.06 Advanced Edition for Linux on Linux Red Hat 5.0 Database/Driver File/Version: N/A Comments: When performing an stress tests with 15-20 users connecting to EAServer 6.3 and instantiating PB NVO Components, PBVM throws exception: 2010-04-03 10:21:20.961 INFO Thread-84 [JaguarServer] _______________________________________________________________________________ 2010-04-03 10:21:21.441 INFO Thread-84 [JaguarServer] PB Heap Manager Exception: 2010-04-03 10:21:21.441 INFO Thread-84 [JaguarServer] allocVM(52330496) failed 2010-04-03 10:21:21.441 INFO Thread-84 [JaguarServer] _______________________________________________________________________________ 2010-04-03 10:21:21.442 INFO Thread-84 [JaguarServer] PB Heap Manager Exception: CR:625776 CR Number:   625776 Product Name:   PB Enterprise Product Component:   DW HTML Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 30 May 2010 Fixed Description When using datawindow.data.htmltable, it is causing the size of edit and icons to change from pb9. The icons are getting cut off. Causing formatting issues for customer migrating from pb 9. CR:625864 CR Number:   625864 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 Sep 2010 Fixed Description When RowCopy() is executed in its own itemchanged event, the value of a ChekBox object is not changed. CR:625927 CR Number:   625927 Product Name:   PB Enterprise Product Component:   Documentation Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Fixed Description Customer faced problem that in the end turned out to be caused by not reimporting the PBDOM objects after migration. This requirement does not seem to be documented at all. Neither in the PB docu/HTML books nor in the rel. bulletin or on migration guide http://www.sybase.com/detail?id=1032777 CR:625934 CR Number:   625934 Product Name:   PB Enterprise Product Component:   ORCA Status:   Open OS:   Windows XP Original Version:   11.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Trying to build a project that builds and deploys COM objects fails with error -21. CR:626415 CR Number:   626415 Product Name:   PB Enterprise Product Component:   DB JDBC Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 21 Jun 2010 Fixed Description Performance problem when calling SyntaxFromSQL using the Oracle JDBC thin driver. Calling SyntaxFromSQL on a large multi-million row table with a non unique index takes a long time when connected through jdbc compared with OCI O10 or odbc driver. CR:626445 CR Number:   626445 Product Name:   PB Enterprise Product Component:   ORCA Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Apr 2010 Fixed 24 May 2010 Fixed Description When using orcascript to deploy an easerver proxy and using the following command in the orca script: build project with overrides "loanclient.pbl" "p_easproxy" "localhost" "9000" "jagadmin" "" If the override info is different than what is stored in the proxy, orcascript is not using the override parameter. It will use what is stored with the proxy. If the server that is stored with the proxy is not running, the following error results: Orca error in 'buildProjectWithOverrides'. Result Code -21. Component builder build for project p_loanclient_easproxy failed An error occurred during the component builder BuildProject method. Last Command Failed CR:626569 CR Number:   626569 Product Name:   PB Enterprise Product Component:   PB Web Services Status:   Closed OS:   Windows XP Original Version:   11.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 May 2010 Fixed Description Fail to call a WebService using a proxy server. CR:626575 CR Number:   626575 Product Name:   PB Enterprise Product Component:   Machine Code Exe Creation Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description PowerBuilder crashes when creating an EXE using a PBD library. CR:626630 CR Number:   626630 Product Name:   PB Enterprise Product Component:   PB.NET WS Deployment Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description OS: Windows XP SP3 Versions and Build #s Tested: PB 11.5.1_4736 Database/Driver File/Version: N/A Comments: Each time you deploy same webservices to msi and run the same installer, msi installer does not detect webservice is already installed and creates new duplicated uninstaller in Add/Remove Programs. Workaround Description  Before reinstalling, first go to Add/Remove Programs in Control Panel and remove the old installation before installing the new one. CR:626643 CR Number:   626643 Product Name:   PB Enterprise Product Component:   PB.NET WebForm Status:   Closed OS:   Windows XP Original Version:   11.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Jun 2010 Fixed Description Our customer develops PB webforms applications that he sells to user's He has one large user that absolutely does not want his clipboard read or written. The IT department has been setup to flag websites that don't comply. PowerBuilder webapps don't comply. Users are able to copy and paste sles on the webapp. This is due to the textbox.js javascript clipboard functions included in the webapp deploy. PB_GetClipboardTextData() is one example function in textbox.js Our customer's question is; How can he develope PB webapps that don't allow clipboad copy and paste? Is there anything he can do? Can he edit the textbox.js and change or delete the clipboard functions? He needs a solution. It is possible to set the user's browser to not allow programatic clipboard operations. But our user does not want to have to enforce this across many users and it's not really a solution (when set to disable it still allows copy and paste). CR:626664 CR Number:   626664 Product Name:   PB Enterprise Product Component:   Windows Ink Control Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Jun 2011 Added to user documentation Description Enumerated values for InkPicture control picturesizemode documented is wrong Workaround Description  Workaround, values should be: inkpicautosize! Inkpiccentered! Inkpicnormal! Inkpicstretched! CR:627012 CR Number:   627012 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Open OS:   Windows 2008 Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description PowerBuilder12 is not supporting next 64bit Windows. Windows Server 2008 64bit/Windows Server 2008 R2/Windows 7 64bit. CR:627090 CR Number:   627090 Product Name:   PB Enterprise Product Component:   SYSAM Status:   Closed OS:   Windows XP Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Apr 2010 Fixed 10 May 2010 Fixed Description Cannot open the PB 12 .NET ide when using a standalone unserved license. Opening the ide results in a trial license has expired error message and the ide shuts down. This problem happens with the unserved license and alternative use customer license. A served license will work on Windows XP, but the SySam 2.0 server won't start on Windows 7 or Windows 2008. CR:627258 CR Number:   627258 Product Name:   PB Enterprise Product Component:   SYSAM Status:   Closed OS:   Windows XP Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 May 2010 Third Party Problem 27 Jul 2010 Fixed Description Two issues with Sysam and PowerBuilder 12.0 on Windows 7 32bit OS: 1) The Sysam 2.0 server would not start as a service on Windows 7. 2) Using Sysam 2.1 (from PowerDesigner) the server did start as a service on Windows 7, but I could not get a PowerBuilder 12 served license to work when the Sysam 2.1 service was hosted on the same machine that PowerBuilder was getting installed on. (Workaround was to use a sysam server that was running on a Windows XP machine.) CR:627355 CR Number:   627355 Product Name:   PB Enterprise Product Component:   PB Web Services Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 May 2010 Fixed Description Execution of the upsert() function of the webservice of salesforce leads to an error from salesforce: INVALID_TYPE: Must send a concrete entity type. CR:627469 CR Number:   627469 Product Name:   PB Enterprise Product Component:   SYSAM Status:   Closed OS:   Windows XP Original Version:   12.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 05 May 2010 Fixed Description Cannot open the PB 12 .NET IDE when using a standalone unserved license. Opening the IDE results in a trial license has expired error message and the IDE shuts down. This problem happens with the unserved license. CR:627635 CR Number:   627635 Product Name:   PB Enterprise Product Component:   MAPI Status:   Closed OS:   Windows 7 Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 06 May 2010 Fixed Description mailAddress function fails on Windows 7. CR:627761 CR Number:   627761 Product Name:   PB Enterprise Product Component:   ORCA Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10 Jun 2010 Fixed Description Customer is using Ant and Oracscript to build a PB app containing EAServer components. He is getting Library refresh errors and the dreaded -20 deploy project return code also. In addition he notes "Also, just a heads-up, we've discovered that orcascript builds of PB components for EAServer fail to "include unreferenced objects" in the PBD - like datawindows and such. We'll also need that fixed, since it basically renders orcascript useless without it." CR:627961 CR Number:   627961 Product Name:   PB Enterprise Product Component:   DW - Runtime Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 25 May 2010 Fixed Description Customer has noticed a problem with the Datawindow QueryMode = YES property in relationship with the Datawindow.Table.Select value. If more than one row of a dddw datawindow contains the same display value, the corresponding data value of the first occurrence is always returned. As an example, if you have John Smith 123 for the first row and John Smith 456 for the second row, choosing John Smith always returns 123. It does not behave like this without the QueryMode set to Yes. CR:628098 CR Number:   628098 Product Name:   PB Enterprise Product Component:   Jaguar Integration Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.5 11 Apr 2013 Fixed 12 Sep 2011 Presently Not Targeted For Any Future Release Of This Product Description When calling a PB component and measuring the memory consumption using PbHeap_dump(2) after two successive calls, the bytes in use increase. CR:628100 CR Number:   628100 Product Name:   PB Enterprise Product Component:   DB Oracle Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Jun 2010 Fixed Description When NLS_Charset='local' and PWDialog is set to 1 upon entering the correct values into the dialogbox it won't allow login, causing ORA-01017 error. No Problem when NLS_Charset set to default (unicode). CR:628102 CR Number:   628102 Product Name:   PB Enterprise Product Component:   PB Web Services Status:   Open OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Ct uses AuthenticationMode = Windows (Basic, Digest) and certificates. CR:628132 CR Number:   628132 Product Name:   PB Enterprise Product Component:   Documentation Status:   Closed OS:   Windows XP Original Version:   11.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 18 Aug 2011 Insufficient priority to fix Description The online help for Component Timeout property from the Properties for EAServer Component Generator: Components tab list: Component timeout Specify how long an active component instance can remain idle between method calls before being automatically deactivated. The default is 0, which means the instance is not automatically deactivated. When specifying timeouts, a resolution of 5 seconds is recommended. However, in EAServer 6.x, when deploying a stateful component the component timeout of 0 default maps to 600 seconds (10 minutes) in EAServer. (Component timeout maps to the passivation timeout.) From cr627420 and easerver group: user wants a timeout of more than 10 minutes, they should set it explicitly --------------------------------------华丽的分割线------------------------------------------------------------------------- Sybase SQL Anywhere数据库恢复工具ReadASADB： 之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具: ReadASADB。 此工具支持ASA v5.0, v6.0, v7.0, v8.0, v9.0, v10.0, v11.0, v12.0, v16.0, v17.0等版本。 能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具。 恢复Sybase SQL Anywhere的工具在国内处于领先水平。 Sybase SQL Anywhere数据库恢复工具ReadASADB功能 能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具 适用于所有的SQL Anywhere版本    包括：5.x,6.x,7.x,8.x,9.x,10.x,11.x,12.x,16.x,17.x 适用于所有的UltraLite版本 能够恢复出来表结构和数据 能够恢复自定义数据类型 能够恢复存储过程等对象的语法 能够导出到目标数据库 能够导出到SQL文件并生成导入脚本 支持多种字符集，包括：cp850、cp936、gb18030、utf8等 能够恢复未加密或者简单加密类型的数据 简单易用 限制：不支持AES加密的数据文件 请参考：研发成功了从Sybase SQL Anywhere的DB文件上恢复数据的工具             SQL Anywhere数据库非常规恢复工具ReadASADB使用介绍 Sybase SQL Anywhere数据库恢复工具ReadASADB适用场景 各种误操作： 误截断表(truncate table) 误删除表(drop table) 错误的where条件误删数据 误删除db或log文件 误删除表中的字段 Sybase SQL Anywhere数据库恢复工具ReadASADB的应用场景： 1.因为物理磁盘故障、操作系统、系统软件方面或者掉电等等原因导致的Sybase SQL Anywhere数据库无法打开的情况； 2.误操作，包括truncate table,drop table,不正确的where条件导致的误删除等； Sybase SQL Anywhere无法打开时，比较常见的错误是：Assertion failed。 如： 1、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Checkpoint log: invalid bitmap page -- transaction rolled back 2、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Page number on page does not match page requested -- transaction rolled back 3、Internal database error *** ERROR *** Assertion failed:200502 (9.0.2.2451) Checksum failure on page 23 -- transaction rolled back 4、File is shorter than expected 5、Internal database error *** ERROR *** Assertion failed: 201116 Invalid free list index page found while processing checkpoint log -- transaction rolled back 6、*** ERROR *** Assertion failed: 51901 Page for requested record not a table page or record not present on page 7、*** ERROR *** Assertion failed: 201417 (7.0.4.3541) Invalid count or free space offset detected on a table page 8、Internal database error *** ERROR *** Assertion failed: 201425 (8.0.3.5594) Invalid count or free space offset detected on a free list page -- transaction rolled back. 9、Internal database error *** ERROR *** Assertion failed: 100702 (8.0.1.2600) Unable to modify indexes for a row referenced in rollback log -- transaction rolled back ------------------------------------------------------------------------------------------- Sybase ASE数据库恢复工具READSYBDEVICE： 一个不依赖数据库管理系统、直接从Sybase数据库设备文件上提取数据的业内领先的恢复工具！ 能够从损坏的Sybase ASE设备文件(.dat)上提取数据的非常规恢复工具。 Sybase ASE数据库恢复工具READSYBDEVICE的主要功能： 被勒索病毒加密数据文件及备份文件情况下的恢复； 系统崩溃只剩下数据文件的情况下的恢复，甚至数据库文件不存在而只有损坏的备份文件情况下的恢复； 因断电、硬盘坏道等造成数据库文件损坏情况下的恢复； delete数据恢复、误update数据恢复、误删除表(drop）恢复、误truncate表恢复 等； 各种Sybase内部系统表损坏、索引错误的修复； master数据库损坏而无法正常运行情况下的恢复； Sybase数据库被标记为可疑，不可用等情况的恢复； Sybase数据库中数据文件内部出现坏块情况下的恢复； Sybase数据库无数据文件但有日志文件的情况下的恢复； Sybase数据库只有数据文件无任何日志文件的情况下的恢复； Sybase数据文件被误删除情况下的碎片提取恢复； 磁盘阵列上的Sybase数据库被误格式化情况下的数据库恢复； 数据库sysobjects等系统表损坏无法正常应用情况下的恢复； Sybase数据库还原数据库出现失败情况下的恢复； Sybase数据库只剩下损坏的备份文件情况下的恢复。 Sybase ASE数据库恢复工具READSYBDEVICE支持的版本： Sybase ASE 11.0.x，11.5.x，11.9.x，12.0.x，12.5.x，15.0.x，15.5.x，15.7.x，16.0.x ------------------------------------------------------------------------------------------- SQL Server数据库恢复工具SQLRescue： 一个不依赖数据库管理系统、直接从SQL Server数据库文件上提取数据的业内领先的恢复工具！ 能够从损坏的SQL Server数据库文件(.mdf)上提取数据的非常规恢复工具。 SQL Server数据库恢复工具SQLRescue的主要功能： 系统崩溃只剩下数据文件的情况下的恢复，即无日志文件或者日志文件损坏情况下的恢复； 断电导致数据库文件损坏情况下的恢复； 硬盘坏道造成数据库损坏情况下的恢复； 数据文件内部存在坏页情况下的恢复； 企业管理器误删除数据表记录，管理软件误删除数据表记录的恢复； 并闩锁错误、格式化、误删除后导致软件不能使用的情况； 无法读取并闩锁页sysindexes失败情况下的修复； 数据文件被误删除情况下的碎片提取恢复； 系统表损坏、索引错误、误删除数据库表、删除记录的数据找回； master数据库损坏而无法正常运行情况下的恢复； 数据文件无法附加情况下的数据恢复； 数据库被标记为可疑，质疑，不可用等情况的恢复； 数据库sysobjects等系统表损坏情况下的恢复； 数据被误(drop、delete、truncate）删除表数据的恢复,误update后的数据恢复等； 还原时报一致性错误，错误823等情况下的数据恢复，各种错误提示的数据库文件修复； 数据库被误格式化等情况下的数据库恢复； 日志收缩造成数据库损坏情况下的恢复； 仅剩损坏的备份文件情况下的恢复。 SQL Server数据库恢复工具SQLRescue技术特点： 只要SQL Server数据库的数据文件存在，我们就有办法帮您从数据文件中找回重要数据。 从数据文件中直接恢复数据 不能附加时直接恢复数据并生成新的数据库 系统表损坏的数据库修复 快速修复SQL 823错误、连接中断错误 SQL Server数据库恢复工具SQLRescue支持的版本： Microsoft SQL Server 7.0, 2000, 2005, 2008, 2008R2, 2012, 2014, 2016, 2017,2019。 +-------------------------------------华丽的分割线------------------------------------------------------------------------- © 2009-2023 Sybase数据库技术，数据库恢复专家- 提供Sybase ASE及Sybase SQL Anywhere数据库修复服务，电话: 13811580958(微信)，QQ: 289965371！We have many years of experience in recovering data from damanged Sybase devices. Contact us by Phone: +86 13811580958 Wechat: 13811580958 Email: 289965371@qq.com 京ICP备2020043699号-2 Powered by WordPress | SiteMap | Baidu Knows | Google Knows | About  置顶