Recording IBM iSeries 5250 Sessions

I'm recording a series of RPG programs on the above mentioned platform. The main program uses function keys to open new programs. there are 7 function keys off the main screen. 5 of them open fine and captivate captures the image recording which funtion key was pressed. 2 of them do nothing specifically F3 and F9, when I press either of those keys Captivate does not capture the recording.
Anyone else witnessed this issue or have a recommendation?

Yes, I was thinking I would just stop and start the recording, it's just strange that only 2 don't work.
Thanks for responding

Similar Messages

Error with DG4ODBC while setting up connectivity from oracle to IBM iSeries AS400 version V7R1

Hi,
I have Enterprise linux 64-bit hosting Oracle 11gR2 64-bit (11.2.0.1) database. I have access to IBM iSeries AS400 version V7R1. I am trying to connect to IBM iSeries from Oracle Database through ODBC connectivity using Database Link. The following is what I have done.
On the Database (Linux) host Installed iSeriesAccess-7.1.0-1.0.x86_64.rpm provided by IBM.
my odbcinst.ini has the following entries:
[PostgreSQL]
Description             = ODBC for PostgreSQL
Driver          = /usr/lib/libodbcpsql.so
Setup           = /usr/lib/libodbcpsqlS.so
FileUsage               = 1
[iSeries Access ODBC Driver]
Description             = iSeries Access for Linux ODBC Driver
Driver          = /opt/ibm/iSeriesAccess/lib64/libcwbodbc.so
Setup           = /opt/ibm/iSeriesAccess/lib64/libcwbodbcs.so
NOTE1           = If using unixODBC 2.2.11 or later and you want the 32 and 64-bit ODBC drivers to share DSN's,
NOTE2           = the following Driver64/Setup64 keywords will provide that support.
Driver64                = /opt/ibm/iSeriesAccess/lib64/libcwbodbc.so
Setup64         = /opt/ibm/iSeriesAccess/lib64/libcwbodbcs.so
Threading               = 2
DontDLClose             = 1
UsageCount              = 1
[iSeries Access ODBC Driver 64-bit]
Description             = iSeries Access for Linux 64-bit ODBC Driver
Driver          = /opt/ibm/iSeriesAccess/lib64/libcwbodbc.so
Setup           = /opt/ibm/iSeriesAccess/lib64/libcwbodbcs.so
Threading               = 2
DontDLClose             = 1
UsageCount              = 1
The odbc.ini has the following entries:
[ODBC Data Sources]
dg4odbc = connection to db2
[dg4odbc]
Driver = /opt/ibm/iSeriesAccess/lib64/libcwbodbc.so
Description=iSeries Access for Linux ODBC Driver
LogonID=
Password=
Address= (IBM host IP Address)
location=Vm520
noprompt=true
system= (IBM host IP Address)
UNICODE=UTF-8
Naming = 0
ConnectionType = 0
CommitMode = 2
ExtendedDynamic = 0
AllowDataCompression = 1
LibraryView = 0
AllowUnsupportedChar = 0
ForceTranslation = 0
Trace = 0
made sure I could connect via ODBC and DSN using the following command:
isql dg4odbc oracle oracle1 -v
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL>
SQLRowCount returns -1
600 rows fetched
SQL>
could query the table in a library on AS400.
The $ORACLE_HOME/hs/admin/initdg4odbc.ora has the following entries:
# This is a sample agent init file that contains the HS parameters that are
# needed for the Database Gateway for ODBC
# HS init parameters
HS_FDS_CONNECT_INFO = dg4odbc
HS_FDS_TRACE_LEVEL = off
HS_FDS_SHAREABLE_NAME=/etc/newlib/libodbc.so
HS_FDS_TRACE_LEVEL = 255
HS_FDS_SUPPORT_STATISTICS=FALSE
# ODBC specific environment variables
set ODBCINI=/etc/odbc.ini
# Environment variables required for the non-Oracle system
The listener entries are as follows:
    (SID_DESC =
      (SID_NAME = dg4odbc)
      (ORACLE_HOME = /opt/oracle/dbs/product/11.2.0/dbhome_1)
      (PROGRAM = dg4odbc)
Stopped and started the listener.
The TNS entry is as follows:
armcdb2 =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = vmw-dev-rmsdb.xxx.vmc)(PORT = 1521))
    (CONNECT_DATA =
    (SID=dg4odbc)
    (HS=OK)
Could tnsping :
oracle@rmsdev[/opt/oracle/dbs/product/11.2.0/dbhome_1/network/admin]$ tnsping armcdb2
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 11-JUL-2013 16:01:23
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/opt/oracle/dbs/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = vmw-dev-rmsdb.xxx.vmc)(PORT = 1521)) (CONNECT_DATA = (SID=dg4odbc)) (HS=OK))
OK (0 msec)
created a public database link as follows:
SQL> create database link samplink connect to "oracle" identified by "oracle1" using 'armcdb2';
Database link created.
When I run a select query I get errors as follows:
SQL> select * from mdiaz.AREMAIL@samplink;
select * from mdiaz.AREMAIL@samplink
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
408
Below is the Trace file of dg4odbc:
Oracle Corporation --- THURSDAY JUL 11 2013 16:06:03.627
Heterogeneous Agent Release
11.2.0.1.0
Oracle Corporation --- THURSDAY JUL 11 2013 16:06:03.627
    Version 11.2.0.1.0
Entered hgogprd
HOSGIP for "HS_FDS_TRACE_LEVEL" returned "255"
Entered hgosdip
setting HS_OPEN_CURSORS to default of 50
setting HS_FDS_RECOVERY_ACCOUNT to default of "RECOVER"
setting HS_FDS_RECOVERY_PWD to default value
setting HS_FDS_TRANSACTION_LOG to default of HS_TRANSACTION_LOG
setting HS_IDLE_TIMEOUT to default of 0
setting HS_FDS_TRANSACTION_ISOLATION to default of "READ_COMMITTED"
setting HS_NLS_NCHAR to default of "AL32UTF8"
setting HS_FDS_TIMESTAMP_MAPPING to default of "DATE"
setting HS_FDS_DATE_MAPPING to default of "DATE"
setting HS_RPC_FETCH_REBLOCKING to default of "ON"
setting HS_FDS_FETCH_ROWS to default of "100"
setting HS_FDS_RESULTSET_SUPPORT to default of "FALSE"
setting HS_FDS_RSET_RETURN_ROWCOUNT to default of "FALSE"
setting HS_FDS_PROC_IS_FUNC to default of "FALSE"
setting HS_FDS_CHARACTER_SEMANTICS to default of "FALSE"
setting HS_FDS_MAP_NCHAR to default of "TRUE"
setting HS_NLS_DATE_FORMAT to default of "YYYY-MM-DD HH24:MI:SS"
setting HS_FDS_REPORT_REAL_AS_DOUBLE to default of "FALSE"
setting HS_LONG_PIECE_TRANSFER_SIZE to default of "65536"
setting HS_SQL_HANDLE_STMT_REUSE to default of "FALSE"
setting HS_FDS_QUERY_DRIVER to default of "TRUE"
HOSGIP returned value of "FALSE" for HS_FDS_SUPPORT_STATISTICS
Parameter HS_FDS_QUOTE_IDENTIFIER is not set
setting HS_KEEP_REMOTE_COLUMN_SIZE to default of "OFF"
setting HS_FDS_GRAPHIC_TO_MBCS to default of "FALSE"
setting HS_FDS_MBCS_TO_GRAPHIC to default of "FALSE"
Default value of 64 assumed for HS_FDS_SQLLEN_INTERPRETATION
setting HS_CALL_NAME_ISP to "gtw$:SQLTables;gtw$:SQLColumns;gtw$:SQLPrimaryKeys;gtw$:SQLForeignKeys;gtw$:SQLProcedures;gtw$:SQLStatistics;gtw$:SQLGetInfo"
setting HS_FDS_DELAYED_OPEN to default of "TRUE"
setting HS_FDS_WORKAROUNDS to default of "0"
Exiting hgosdip, rc=0
ORACLE_SID is "dg4odbc"
Product-Info:
Port Rls/Upd:1/0 PrdStat:0
Agent:Oracle Database Gateway for ODBC
Facility:hsa
Class:ODBC, ClassVsn:11.2.0.1.0_0008, Instance:dg4odbc
Exiting hgogprd, rc=0
hostmstr:          0:   HOA After hoagprd
hostmstr:          0:   HOA Before hoainit
Entered hgoinit
HOCXU_COMP_CSET=1
HOCXU_DRV_CSET=871
HOCXU_DRV_NCHAR=873
HOCXU_DB_CSET=871
HOCXU_SEM_VER=112000
Entered hgolofn at 2013/07/11-16:06:03
HOSGIP for "HS_FDS_SHAREABLE_NAME" returned "/etc/newlib/libodbc.so"
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLAllocHandle
symbol_peflctx=0xaab7c2f0
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLBindCol
symbol_peflctx=0xaab7c9d0
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLBindParameter
symbol_peflctx=0xaab7cb6c
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLCancel
symbol_peflctx=0xaab7d416
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLDescribeParam
symbol_peflctx=0xaab7f7dc
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLDisconnect
symbol_peflctx=0xaab7f978
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLEndTran
symbol_peflctx=0xaab7fe42
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLExecute
symbol_peflctx=0xaab808ac
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLFetch
symbol_peflctx=0xaab80b5c
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLFreeHandle
symbol_peflctx=0xaab816aa
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLFreeStmt
symbol_peflctx=0xaab82144
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetData
symbol_peflctx=0xaab83ad8
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetEnvAttr
symbol_peflctx=0xaab84e42
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetFunctions
symbol_peflctx=0xaab84fce
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLMoreResults
symbol_peflctx=0xaab85a0a
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLNumResultCols
symbol_peflctx=0xaab85fba
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLParamData
symbol_peflctx=0xaab86102
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLPutData
symbol_peflctx=0xaab871fc
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLRowCount
symbol_peflctx=0xaab87364
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLSetEnvAttr
symbol_peflctx=0xaab89054
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLSetDescRec
symbol_peflctx=0xaab88e20
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLColAttributeW
symbol_peflctx=0xaab7d6ba
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLColumnsW
symbol_peflctx=0xaab7e264
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLConnectW
symbol_peflctx=0xaab7e6b4
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLDescribeColW
symbol_peflctx=0xaab7f39e
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLDriverConnectW
symbol_peflctx=0xaab7fa9a
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLExecDirectW
symbol_peflctx=0xaab805e6
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLForeignKeysW
symbol_peflctx=0xaab80de6
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetConnectAttrW
symbol_peflctx=0xaab82714
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetDescFieldW
symbol_peflctx=0xaab83c76
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetDescRecW
symbol_peflctx=0xaab83fbe
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetDiagFieldW
symbol_peflctx=0xaab8448a
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetDiagRecW
symbol_peflctx=0xaab84916
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetInfoW
symbol_peflctx=0xaab85136
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetStmtAttrW
symbol_peflctx=0xaab85456
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLGetTypeInfoW
symbol_peflctx=0xaab8576e
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLPrepareW
symbol_peflctx=0xaab863b0
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLPrimaryKeysW
symbol_peflctx=0xaab8667c
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLProcedureColumnsW
symbol_peflctx=0xaab86a14
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLProceduresW
symbol_peflctx=0xaab86e64
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLSetConnectAttrW
symbol_peflctx=0xaab874ac
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLSetStmtAttrW
symbol_peflctx=0xaab896c8
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLSetDescFieldW
symbol_peflctx=0xaab88b00
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLStatisticsW
symbol_peflctx=0xaab89e64
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Entered hgolofns at 2013/07/11-16:06:03
libname=/etc/newlib/libodbc.so, funcname=SQLTablesW
symbol_peflctx=0xaab8a668
hoaerr:0
Exiting hgolofns at 2013/07/11-16:06:03
Exiting hgolofn, rc=0 at 2013/07/11-16:06:03
HOSGIP for "HS_OPEN_CURSORS" returned "50"
HOSGIP for "HS_FDS_FETCH_ROWS" returned "100"
HOSGIP for "HS_LONG_PIECE_TRANSFER_SIZE" returned "65536"
HOSGIP for "HS_NLS_NUMERIC_CHARACTER" returned ".,"
HOSGIP for "HS_KEEP_REMOTE_COLUMN_SIZE" returned "OFF"
HOSGIP for "HS_FDS_DELAYED_OPEN" returned "TRUE"
HOSGIP for "HS_FDS_WORKAROUNDS" returned "0"
HOSGIP for "HS_FDS_MBCS_TO_GRAPHIC" returned "FALSE"
HOSGIP for "HS_FDS_GRAPHIC_TO_MBCS" returned "FALSE"
Invalid value of 64 given for HS_FDS_SQLLEN_INTERPRETATION
treat_SQLLEN_as_compiled = 1
Exiting hgoinit, rc=0 at 2013/07/11-16:06:03
hostmstr:          0:   HOA After hoainit
hostmstr:          0:   HOA Before hoalgon
Entered hgolgon at 2013/07/11-16:06:03
reco:0, name:oracle, tflag:0
Entered hgosuec at 2013/07/11-16:06:03
Exiting hgosuec, rc=0 at 2013/07/11-16:06:03
Entered hgopoer at 2013/07/11-16:06:03
hgopoer, line 233: got native error 408 and sqlstate 410; message follows...
408
Exiting hgopoer, rc=0 at 2013/07/11-16:06:03
hgolgon, line 193: calling SQLSetConnectAttr got sqlstate 410
Exiting hgolgon, rc=28500 at 2013/07/11-16:06:03 with error ptr FILE:hgolgon.c LINE:193 FUNCTION:hgolgon() ID:Connection Attribute: TRACE
hostmstr:          0:   HOA After hoalgon
RPC Calling nscontrol(0), rc=0
hostmstr:          0: RPC Before Exit Agent
hostmstr:          0:   HOA Before hoaexit
Entered hgoexit at 2013/07/11-16:06:03
Exiting hgoexit, rc=0
hostmstr:          0:   HOA After hoaexit
hostmstr:          0: RPC After Exit Agent
I have looked up the errors on Oracle forums and could not get any valuable help anywhere.
Can someone kindly help out where I am going wrong?
Thanks,
Ram.

Hello kgronau,
Thank You very much for your recommendations. I removed the parameter HS_FDS_TRACE_LEVEL = 255.
I added HS_FDS_FETCH_ROWS=1 and also HS_NLS_NCHAR = UCS2
Tested my sql statement, which yielded the result as follows:
SQL> select * from mdiaz.AREMAIL@samplink;
select * from mdiaz.AREMAIL@samplink
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
㈵″㠵6
SO I thought I would give a try of removing the line HS_NLS_NCHAR = UCS2
and again tested my sql statement and it worked like a charm!!!!
I tested a count(*) and got the results back.
SQL> select count(*) from mdiaz.AREMAIL@samplink;
COUNT(*)
       600
I really appreciate your valuable pointers and help.
Thanks once again!!!
Ram.

UCCX 9.0.1 Datasource to IBM iSeries

I am doing an upgrade from UCCX 7.0.2 to 9.0.1.
The UCCX 7.0.2 has an ODBC driver connection to an IBM iSeries DB server using an iSeries driver. I need to replicate this connection on UCCX 9.0.
On UCCX 9.0 I only have the ability to use a few type of drivers, JDBC DB2 driver being one of them. I have tried using the following drivers:
db2jcc.jar
db2jcc4.jar
I have also loaded the customer supplied db2jcc_license_cu.jar
Both of the drivers load successfully under the com.ibm.db2.jcc.DB2Driver class, but when I try to make a Database Source connection within UCCX the test connection always fails. I have created a new DB account so I have verified that the username and password are correct.
I have tried these different formats when creating the Database Source. I don't know what port number I should be using. I saw 50000 mentioned in a few forums.
jdbc:db2//10.80.1.100:50000/val
jdbc:db2//10.80.1.100/val
No matter the syntax the Test Connection always fails.
Thanks,
Brian Corbet

We recently took a customer from CCX 7.x (Windows based) to 9.x (Cisco UCOS based) and ran into this issue.
Problem:
Connecting via JDBC to an iSeries DB2 database
description: Getting an error when trying to add an iSeries DB2 DataSource to the CCX server. Adding the Datasource fails. In the CCX Engine logs, you see something similar to the following:
[SQLException@185bf33] Message = [jcc][t4][10509][13454][4.16.53] Connection to the data server failed. The IBM Data Server for JDBC and SQLJ license was invalid
%MIVR-LIB_JDBC-7-UNK:or was not activated for the DB2 for z/OS subsystem. If you are connecting directly to
%MIVR-LIB_JDBC-7-UNK:the data server and using DB2 Connect Unlimited Edition for System z, perform the
%MIVR-LIB_JDBC-7-UNK:activation step by running the activation program in the license activation kit.
%MIVR-LIB_JDBC-7-UNK:If you are using any other edition of DB2 Connect, obtain the license file,
%MIVR-LIB_JDBC-7-UNK:db2jcc_license_cisuz.jar, from the license activation kit, and follow the installation
%MIVR-LIB_JDBC-7-UNK:directions to include the license file in the class path. ERRORCODE=-4230, SQLSTATE=42968
Solution:
1) The customer provided the db2jcc_license_cisuz.jar file, part of the “DB2 Connect” file set, which they purchased from IBM.
2) I installed the Java SE JDK version 8_20 (not sure that the JDK version actually matters except later when I set my PATH).
3) I copied the db2jcc4.jar file from the 10.5 driver and the db2jcc_license_cisuz.jar file from the provided DB2 Connect file set to the root of my c: drive.
4) I ran the following commands in Windows Command Prompt to combine the jar files into a single file:
PATH=%PATH%;C:\Program Files\Java\jdk1.8.0_20\bin
c:
cd \
mkdir tmp
cd tmp
jar -xf ../db2jcc4.jar
jar -xf ../db2jcc_license_cisuz.jar
cd ..
jar -cvf combined.jar -C tmp .
5) I browsed in CCX Administration to Subsystems > Database > Drivers, chose my file “combined.jar” file (C:\combined.jar) and selected "com.ibm.db2.jcc.DB2Driver” from the drop down box. I clicked upload and it accepted it.
6) I browsed in CCX Administration to Subsystems > Database > Datasource and built my datasource. I entered my DSN name, username, password, confirmed the password, chose “com.ibm.db2.jcc.DB2Driver” from the drop down box, and entered my JDBC URL - jdbc:db2://<iSeries IP Address>:446/SXXXXXXX - where, SXXXXXXX is the database name.
7) I then went into the Datasource and tested. It tested successfully.
This allowed us to connect to the customer’s iSeries database.
Please note that after we fixed this issue, we ran into another one. Here's a description of that issue and how we resolved it.
Problem:
Inserting Rows to a non-journaled iSeries DB2 database
Description: Getting an error when we try to insert or update an iSeries DB2 database, using the DB Write Step. This was working before in CCX 7.x (Windows based) when the connection was using ODBC. The CCX engine is successfully able to connect to the customer database via JDBC, however, we are seeing something similar to this in the CCX Engine logs when we try to do database writes (DB Write in CCX script):
%MIVR-LIB_JDBC-7-UNK:com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-7008, SQLSTATE=55019, SQLERRMC=DATABASENAME ;3, DRIVER=4.16.53
Solution:
The key to this problem turned out to be that the customer database was not journaled. IBM provided useful information in this regard. In particular, the following IBM tech note indicates that they do NOT support manipulating the JDBC driver parameters on the iSeries. Instead, either the database must be journaled, or you must use “WITH NC” (omitting the quotes) at the end of your INSERT or UPDATE SQL query (at the end of our DB Write step) . When we use “WITH NC”, the database inserts work without error.
See this link for more details.
http://www-01.ibm.com/support/docview.wss?uid=swg21676715

BizTalk Administration Console problem after installing IBM iSeries Access

Hi,
We have a Biztalk Server 2010 environment on Windows Server 2008 R2 with SQL server on separate machine.
After installing IBM iSeries Access we get errors in Biztalk Administration Console, especially the Host Instance and Adapter information cannot be loaded.
Except for the errors in Adminsitration Console, the Biztalk installation seems to be working fine, so the integration processes doesn't seem to be affected.
We get the following error:
BizTalk Server cannot access SQL server. This could be due to one of the following reasons:
1. Access permissions have been denied to the current user. Either log on as a user that has been granted permissions to SQL and try again, or grant the current user permission to access SQL Server.
2. The SQL Server does not exist or an invalid database name has been specified. Check the name entered for the SQL Server and database to make sure they are correct as provided during SQL Server installation.
3. The SQL Server exists, but is not currently running. Use the Windows Service Control Manager or SQL Enterprise Manager to start SQL Server, and try again.
4. A SQL database file with the same name as the specified database already exists in the Microsoft SQL Server data folder.
Internal error from OLEDB provider: "The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception." (WinMgmt)
I tried to uninstall the IBM iSeries Access, but the problem remains.
This issue is related to this post
http://social.technet.microsoft.com/Forums/en-US/6f371f45-813c-48d8-80e3-bd94e00bf5dd
But this post seem to miss a solution.
Thanks fo your help with this!
BR
Samuel
SamueL J

Hi and thanks for your help!
The machine.config did it :)
According to this link there is a known issue with the IBM iSeries Access installation which removes the proper permissions from the machine.config and therefore Biztalk Administration Console stops working correctly.
http://www-01.ibm.com/support/docview.wss?uid=nas284158c400658982b86257611003c6d21
BR
Samuel
SamueL J

Has anyone successfully captured a Training or Assessment for IBM iSeries Apps

I just got CP5. I am working on a project where I need to create training and assessment simulation for an IBM iSeries application. ISeries applications must be run in a mainframe emulator and are text command in tensive. CP4 did not capture text entries or command entries, I guess becuse the fields are not GUI text boxes. I had to do text entries manually. Has this changed in CP5? Has anyone successfull done a capture of an iSeries app using the IBM emulator?

I just got CP5. I am working on a project where I need to create training and assessment simulation for an IBM iSeries application. ISeries applications must be run in a mainframe emulator and are text command in tensive. CP4 did not capture text entries or command entries, I guess becuse the fields are not GUI text boxes. I had to do text entries manually. Has this changed in CP5? Has anyone successfull done a capture of an iSeries app using the IBM emulator?

Sequencing the IBM iSeries Access Client 7.1

Hey All,
I was wondering if anybody has experience in sequencing the IBM iSeries Access Client 7.1...
We're currently trying to sequence this application under Windows 7 Enterprise (x86) with the App-V4.6 SP1 Sequencer. We've checked the Windows 7 compatibility of this version and it is supported. Every function of the application is working during the monitoring
phase of the sequence process. The main function we're (currently) interested in is the Emulator with the SSL encryption to our AS400 mainframe. This function requires the SSL-option to be installed. We've installed this with the rest of the application during
our sequencing and during the monitoring phase, we're able to connect to the mainframe.
However, when we transfer the finished sequence to a test system, the Emulator pops up with an error message "SSL option is not installed". After some repackaging and investigation, we've managed to eliminate all the file exclusion that occured during our
sequencing process. This includes a lot of "dirt" into the sequence but at least gave us the confidence that everything that was installed by the setup was also included in the Sequence. We've also excluded the Windows CA store as one of the possible causes.
The IBM iSeries Access Client uses it's own SSL encryption methods.
My question to you all is. Has anyone ever succesfully packaged the IBM iSeries Access Client V7R1 on Windows 7 Enterprise and has anyone encountered/solved the issue we're currently facing?
Thanks in advance for your time and effort!
Microsoft Exchange Server enthousiast. "This is your M drive. This is your M drive after a virus scan. Get the picture?" "Friends don't let friends virusscan the M-Drive"

The option installs the ability to use encrypted connections to your AS400 mainframes. The IBM client installs an extra program in %CSIDL_PROGRAM_FILES%\ibm\gsk7.
Unfortunately there's no exclusion in the Sequence that would point to anything crucial. The IBM client creates a folder in the "My Documents" folder which is (ofcourse) excluded from the Sequence. Other then that only the following is excluded:
<MOREINFO DESCRIPTION="The unsupported shell extensions detected are as follows:">
<ITEM DESCRIPTION="HKLM\SOFTWARE\Classes\AS400System\ShellEx\ContextMenuHandlers"/>
<ITEM DESCRIPTION="HKLM\SOFTWARE\Classes\AS400System\ShellEx\PropertySheetHandlers"/>
<ITEM DESCRIPTION="HKLM\SOFTWARE\Classes\Drive\ShellEx\DragDropHandlers"/>
<ITEM DESCRIPTION="HKLM\SOFTWARE\Classes\Printers\ShellEx\ContextMenuHandlers"/>
But in my oppinion this should not be something that will block the functions of the application itself (since this is drag/drop handler for the seperate file transfer client...)..
But correct me if i'm wrong ofc.
Microsoft Exchange Server enthousiast. "This is your M drive. This is your M drive after a virus scan. Get the picture?" "Friends don't let friends virusscan the M-Drive"

Can't access IBM mainframe 3270 session via SSL self-signed cert.

Can't access IBM mainframe 3270 session via SSL self-signed cert since sometime last week. Using Mochasoft tn3270 lite on android works fine but iPad ios7 says "IBM mainframe has closed the session". Any clues would be appreciated.

I'm thinking the problem may be the IBM cert is 1024 bit. Investigating choices to implement 2048 bit cert into IBM.

UFT 12.0 Automation feasibility on Main Frame emulators [IBM TN 5250, TN 3270]

Hi All,
We have an applicaiton which runs on AIX Operating system with emulator IBM TN 5250 with Websphere, we wanted to to know whether UFT 12.0 can suppport these technologies for automation testing.
Need what add-in is required and what kind of setup we need to do?
please share your thoughts.
Regards,
A M Varaprasad

Hi,
Please check the following dicussion:
http://h30499.www3.hp.com/t5/Unified-Functional-Testing/Terminal-Emulator-SmarTerm-Configuration-for...
You may want to use that forum to get more info.
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Windows Server 2012R2 kerberos authetication failure with IBM iSeries

Hi all,
I've an IBM iSeries in my environment configured to use kerberos authentication, this type of SSO works fine from 2 years. Every client Windows 7 or Windows 8 works fine.
Now I'm planning to deploy Windows 8.1 and Windows Server 2012R2.
I've made a lot of attempts:
Windows 2012 -> works
Windows 8 -> works
Windows 2012R2 -> does not works
Windows 8.1 -> does not works
All the server and workstation involved in thees attempts belong to the same OU and the same user are utilized.
It seems clear to me that Windows 8.1 / 2012R2 has a different behaviour with kerberos authentication but I don't found anything on the technet.
Please note that all DC are Windows server 2008R2 by two years.

Hi, any news for your problem ?
This setup should work ok.. Any firewall running on the 2012R2 or 8.1 ? did you checked the security log on the DC to see why the ticket was refused ? etc..
Regards, Philippe
Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!

Setting up Secure connection with DB2 database on IBM iSeries

We have requirement to setup Secure connection with DB2 database on IBM iseries system. currently we are using ODBC type of connectivity which is not secure. Can anyone help how to set up Secure connectivity. below are the system details . . Application - IDQ - 9.6.0 Database - DB2 on IBM iSeries AS400

We have requirement to setup Secure connection with DB2 database on IBM iseries system. currently we are using ODBC type of connectivity which is not secure. Can anyone help how to set up Secure connectivity. below are the system details . . Application - IDQ - 9.6.0 Database - DB2 on IBM iSeries AS400

WLS 8.1.2 on SuSE Linux 8 / IBM iSeries Model 890

We will be installing WLS 8.1 SP2 on a SuSE Linux 8 logical partition (LPAR). The
hardware is an IBM iSeries Model 890 (Power 4).
The IBM platform is new to me, let alone LPAR's. What kind of challenges will
we cross with shared resources like RAM, CPU, etc?
Has anyone had any experience working with WLS on a logical partition?

Look, nobody should be going to anything other than 901 on 7.2.
Do you like to waste your time? Fastcenter sells these systems,
they install without a flaw and they're rock solid. Why install
a version that's unsupported ?!?

Error when creating a linked server to IBM iSeries AS/400

I am migrating databases from SQL Standard 2005 (32 bit) to SQL Standard
2012 (64 bit) and getting errors when I create the needed Linked Servers to our IBM as/400. I scripted the as400 linked server from the 2005 server and created it on the 2012 server:
EXEC master.dbo.sp_addlinkedserver @server = N'AS400', @srvproduct=N'DB2 UDB for iSeries', @provider=N'MSDASQL', @datasrc=N'AS400'
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'AS400',@useself=N'False',@locallogin=NULL,@rmtuser=N'USER_NAME',@rmtpassword='PSSWD'
(plus various sp_serveroptions)
I then verified that the MSDASQL Provider "Allow Inprocess" was checked and the Linked Server is listed as using the provider but when I try to view the objects under the "AS400" Linked Server I get an error saying: Cannot initialize the
data source object of OLE DB provider "MSDASQL" for linked server "AS400". (Microsoft SQL Server, Error: 7303)
I was told to download and install OLEDB provider for DB2. I downloaded DB2OLEDBV4 but when I try to install it I try to install it I get a OK Box saying: "Microsoft OLE DB Provider for DB2 requires the Microsoft SQL Server 2008 or later
version. Ensure that this version is fullfilled before installing Microsoft OLE DB Provider for DB2." when I click OK, I get "Setup was interrupted before Microsoft OLE DB Provider for DB2 could be completely installed" and the install
exists. I am installing on SQL 2012!
Can anyone please advise...

Hi,
Based on your description, we know that you got an error when you installed the OLEDB provider for DB2. Microsoft OLE DB Provider for DB2 V4.0 is needed If you use SQL Server 2008 R2 or SQL Server 2012 to connect to IBM DB2 databases.When you install the
OLEDB provider for DB2 V4.0, we need to make sure that the system meets the following requirements:
• Windows Server 2008 R2 SP1 or Windows 7 SP1 or Windows Server 2008 SP2.
• Microsoft SQL Server 2012 (Enterprise, Developer or Evaluation Edition) or Microsoft SQL Server 2008 R2 (Datacenter, Enterprise, Developer or Evaluation Edition) is installed.
• Microsoft .NET Framework 4.0.
As your post,it seems that you have installed SQL Server 2012 Standard Edition,this edition is not supported by Microsoft OLEDB Provider for DB2 V4.0. I recommend you to upgrade the standard edition to enterprise edition and reinstall the OLEDB Provider.You
can try this method and if you have any questions,please feel free to revert.
For more detailed information, you can review the following link.http://msdn.microsoft.com/en-us/library/hh873008(v=sql.110).aspx
Thanks
Lydia Zhang

Realistic recording expectations for upcoming session

I'm doing some band recording this weekend and want to get an idea of how many inputs and Logic softsynths I can be recording simultaneously.
I have an MOTU 828mkII. Our drummer will be bringing a Presonus DigiMAX that we'll be hooking to the MOTU via lightpipe, and I'll be plugging in my Yamaha DG Stomp via the S/PDIF in.
Odds are we'll be using the 2 mic ins on the MOTU, all 8 Presonus inputs, at least 4 of the line inputs, the S/PDIF in, and likely up to two Logic instruments and maybe a loop or two... all at once. (So, appx. 15 audio signals plus the synths.) We'll be recording at 24/48 (48 is the best the DigiMAX can do).
Given my system (a brand new dual G5 running 7.1), is this feasible?
My last system was a G4-upgraded B&W G3 which, naturally, mostly puked when we tried to record on this scale. I was assuming this would be cake for a dual G5, but I honestly don't know if I'm setting my expectations too high.
FYI, there is close to zero possibility that I will be able to make any changes to my setup before the weekend (e.g., adding RAM... maybe). Ergo, advice to drastically upgrade equipment will fall on deaf ears.
Thanks in advance for any insight.

It should be able to handle it. Just test it thoroughly before the session. Knowing how to tune/troubleshoot your system is necessary if you're running a G5 or a 7600. For your tests start with just Audio-no Audio Instruments, introduce them later.

Is anyone out there recording multi player audio sessions on logic

I using an apogee 24 input system (symphony), logic 8.01. osx 10.4.11, macpro 2x266, 3 gig. I have been running logic for about 2 years. I am a big fan of the features and the especially the sound of logic.
I have been recording multi player sessions (session players and bands) in Pro tools TDM and HD for many years and would love to work strictly in logic.
I have recently been experimenting with recording some multi player audio/midi sessions with Logic. something like:
drums-10 audio inputs
bass-2 audio inputs
acou gtr 2 audio inputs
ele gtr 2 audio inputs
keys -midi controller-virtual inst.
click/loop-virtual inst
The Apogee hardware seems to be very solid ,and sounds great but I have run into some difficulties with logic's interface in these multi-player sessions.
1. The record enable status of various channels can be accidently turned on or off by selecting another channel. this makes it very tricky to adjust monitor volumes,sends, inserts and so on when trying to set-up a mix for the players.
2. when punching in and out there is a gap (hic-up) in the audio playback shortly after you punch out and also an artifact (small region) is often generated at the point of the punch out. ----set-up: punch on the fly,auto input, replace record.
3. after making a pass with the band and attempting listen. the faders are not active (on audio channels only) while the channels are record armed. So if one wants to adjust a playback/monitor volume the track has to be taken out of record ready which cuts the line of comunication between the players and the control room.
4. there are some serious problems editing audio on grouped channels. IE. group all drums and cut up the regions and do various edits the regions with-in the groups sometime don't act like they are grouped.
There seems to be little or no discussion of multi-player audio recording in any of the forums.
Is anyone out there tracking in a similar set-up and if so are any of these things causing problems for you
Thanks

thanks for the response
I do use the group record enable at times but the group situation in Logic is pretty cumbersome and often times one or more of the group may not be included in the current take so it ends up being a wash as far as convienence goes.
the independent monitoring status is great for what it is intended for but does not affect the situation of the faders not functioning when you monitor audio previously recorded on a record enabled track.
this problem did not exist in lp7 so I feel that it is an oversight or something that fell through the cracks on LP8
my set up is- replace record, auto input and I always have punch on the fly activated. Something I didn't mention in my earlier post about my set-up is, I am using software monitoring. The apogee symphony card is designed and has the speed to through put with about the same(1.6 millsec.)time delay as protools hd. Because I am recording 16 to 20 tracks at once in the box It seems to make sense to work this way. The apogee set-up I am using is 24 in and only 8 out.
with this set-up The hic-cup happens every time just shortly after punch out. this happens on every logic set-up I have ever used in various studios and hardware including an logic demo set-up by apple that I recently went to.
please check it out, it's a simple test
punching in and out is such an important part of audio recording it should be totaly seamless
these problems can be fixed, so I am just trying to raise the awareness of these issues
thanks
ml

Recording of a MS Session via MIO Record Panel

Hi,
I wanna record a Mainstage Session via athe Rcordig Panel of the MIO v.5 Software.
Is that possible?
With regards
Markus

Hi Markus, not sure if you're still out there for this, but I'll give a go. Mainstage will record the audio of an output pair, which you can set in preferences under Audio tab. So instead of recording in Mainstage, you want to record in MIO Console. Record-enable the mixer strip(s) in MIO mixer (making sure you have assigned the direct outs to a firewire bus, otherwise the little "R" will be grayed out). The downside is that you will have to mouse the record button in the Record Panel, instead of the handy button on your guitar or wii remote drumsticks or whatever.
I send all the tracks in Mainstage (3 in my live setup) separate outputs and sum the tracks in the MIO mixer. Metronome goes out 17-18 to the monitor mix. It would be rad if Mainstage could send Mono outs. For a nice recording, I'll just record enable all the tracks in the MIO and mix them later in Logic. The latency readout in Mainstage is a really nice little tool for mixing alignment. It helps to record the metronome out if you're working with that, it's a nice quick&dirty timecode and helps to align other things later. I hope that was clear and helpful, it's a relatively simple operation so just ask to clarify if i've bungled the explaination or didn't understand what you were asking. chxxrs, jay

Recording IBM iSeries 5250 Sessions

Similar Messages

Maybe you are looking for