|
Results |
|
Pie chart gives error "Input string was not in a correct format"
Pie chart gives error " Input string was not in a correct format "
|
|
|
SBM: Error message "Input string was not in a correct format" in Composer
The issue is that Composer remembers current format type and stores it when a new cell is focused. However it doesn't update the stored value when the cell is boolean or enumeration.
|
|
|
Serena StarTool DA CICS User Guide
... 25, 27 exiting Clear key 21 format control block 49–50 program source 42 program source selection 37 transaction ID summary 23 transaction IDs 23 scrolling DOWN command 15 LEFT command 19 RIGHT command 20 sub-parameters described 21 UP command 21 SEARCH command 20 searching addresses by register contents 18 control blocks 50 dump character string 20 FIND command 16 last character 20 RETAIN database 60 selecting database 25, 27 dump to analyze 25 dumps for analysis 30 server functions 25, 27 short format 50 source code compiler input 37 described 37 translator input ...
|
|
|
Serena StarTool DA CICS User’s Guide
... 21, 23 exiting Clear key 18 format control block 44, 45 program source 38 program source selection 34 transaction ID summary 19 transaction IDs 19 scrolling DOWN command 14 LEFT command 16 RIGHT command 17 sub-parameters described 18 UP command 17 SEARCH command 17 searching addresses by register contents 15 control blocks 45 dump character string 17 FIND command 14 last character 17 RETAIN database 54 selecting database 21, 23 dump to analyze 22 dumps for analysis 26 server functions 21, 23 short format 45 source code compiler input 34 described 33 translator input ...
|
|
|
Serena StarTool DA CICS User Guide
scrolling DOWN command 18 LEFT command 22 RIGHT command 22 sub-parameters described 23 UP command 23 SEARCH command 23 searching addresses by register contents 21 control blocks 72 dump character string 23 FIND command 19 last character 22 RETAIN database 81 selecting CICS dumps 37 database 45, 47 dump to analyze 46 dumps 32 duplicate dump processing 38 dumps by abend code example 37 dumps for analysis 50 transactions 36 server functions 45, 47 short format 72 soft-landing field 34 source code compiler input 59 described 58 translator input 64 Source Listing Management screen ...
|
|
|
String Changes from 2009 R1 to 2009 R2
Common logger will not be used. ... exists and has correct settings. IDS_GRID_KEYNAV9 = Press UP, DOWN, LEFT, RIGHT arrow keys to move cell ... IDS_GRID_UNSPECIFIEDERROR = Unspecified format error ... Modified strings : ... IDS_F2_MSG_WSINVOKER_FAILED_TOGETPARSER = Unable to locate parser for input parameter: {1} {0} ... IDS_F2_MSG_WSINVOKER_NO_INPUTPARAM = Unable to find web service input parameter for parameter index: {1} {0}
|
|
|
dim-10 : MsgX() does not correctly handle %%s in string formats
- Warning: Lifecycle Status has been reset... - Warning: The item has moved from 1.data.s%2.data.s3.data.s%4.data.s... This is because the MsgX() routine is not correctly handling the format for the two %% put together as two separate data segments rather than a %%s call which would result in a %s (printf format )
|
|
|
cDate in appscripts no longer accepts German date strings as input
In SBM 10.1.5.2 it was possible to send date strings in German date format to appscripts and use the cDate() function to cast them to a date object. Since 11.2 SBM only accepts US, UK and ISO date formatted strings (i.e. 01/30/2017, 30/01/2017 or 2017-01-30)
|
|
|
KM-DIM10: Migration of newline characters from Unix to Windows format isn't correct
Newline characters in the Unix format after migration are changed for newline characters in the Windows format. At the Validation stage file's contents we get an error (Unix and Windows breakes of strings are compared).
|
|
|
DIM10: Report Builder error - Ora-01830: Date format picture ends before converting entire input string
DIM10: Report Builder error - Ora-01830: Date format picture ends before converting entire input string
|
|
|