User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools


mantisbt:systemi

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
mantisbt:systemi [2007/02/01 13:40] slashsplatmantisbt:systemi [2011/12/14 14:54] (current) – The page rendering was broken (maybe since new PHP version on mantisbt.org). Added new line to fix it at end of file. atrol
Line 3: Line 3:
 Mantis support for IBM System i platform (AS/400, iSeries) and DB2. Mantis support for IBM System i platform (AS/400, iSeries) and DB2.
  
-[[MySQLi5|Installing MySQL on System i]]+===== [[MySQLi5|Installing MySQL on System i]] ===== 
  
 http://dev.mysql.com/downloads/mysql/5.0.html#downloads\\  http://dev.mysql.com/downloads/mysql/5.0.html#downloads\\ 
Line 133: Line 134:
 Save with F2 and exit with F3. Save with F2 and exit with F3.
  
 +At this time, you should end and re-start PHP from the green screen menu at ZENDCORE/ZCMENU.  When it starts back up, everything should be operational.
  
  
Line 139: Line 140:
  
 ---- ----
-[[Mantisi5|Installing MANTIS]]+---- 
 +---- 
 +---- 
 +===== [[Mantisi5|Installing MANTIS]] ===== 
  
 Obtain the latest stable version of Mantis from http://sourceforge.net/project/showfiles.php?group_id=14963&package_id=166159 Obtain the latest stable version of Mantis from http://sourceforge.net/project/showfiles.php?group_id=14963&package_id=166159
Line 156: Line 161:
  
  
-The Mantis system uses two configuration files.  The default file config_defaults_inc.php is  not to be modified.  All modifications to the configuration go into config_inc.php, which is read AFTER config_defaults_inc.php, and therefore overrides it.  Following are some setting that should be set in config_inc.php, most of them will need to be added:+Once that is complete, you should modify the default configuration by editing the config_inc.php file in the main folder of your Mantis installation.  The Mantis system uses two configuration files.  The default file config_defaults_inc.php is  not to be modified.  All modifications to the configuration go into config_inc.php, which is read AFTER config_defaults_inc.php, and therefore overrides it.  Following are some setting that should be set in config_inc.php, most of them will need to be added:
  
  
Line 218: Line 223:
  
 ---- ----
-[[DB2i5|Using native i5 DB2/400]]+===== [[DB2i5|Using native i5 DB2/400]] ===== 
 + 
 +Issues of concern 2007-02-06 
 + 
 +==== A. install.php user error ==== 
 + 
 +=== NOTE: /www/zendcore/htdocs/md/config_inc.php should NOT exist prior to running install.php. === 
 + 
 +/www/zendcore/htdocs/md/admin/install.php will not work.  When run with the following parms (fields only in order): 
 + 
 +db2 (experimental)\\  
 +## system database name from DSPRDBDIRE AS/400 command "Relational database" field\\  
 +S1071FDD\\  
 +PHP_IRA\\  
 +p0okmju7yg\\      
 +## I tested with incrementing numbers for xxx, got up to 024, use a new one each time you run install.php\\  
 +MANTISxxx\\  
 +## BOTH pw's are required, you cannot leave user blank\\  
 +PHP_IRA\\  
 +p0okmju7yg\\  
 +## box below is unchecked\\  
 +[ ] Print SQL...\\  
 +## then click\\  
 +[Install...]\\  
 + 
 +The LIBRARY *IS* being created with the database collection and journal, but the tables and indexes are not.  The database is created by the admin but the tables are made by the user.  The diff in the code for the two operations is: 
 +  
 +FROM: /md/admin/install.php 
 +TO CREATE DB which works 
 +   $g_db = ADONewConnection( $f_db_type ); 
 +   $t_result = $g_db->Connect( $f_hostname, $f_admin_username, $f_admin_password ); 
 + 
 +The 9th green message at the top of the screen shows that the "Attempting to connect to database as ADMIN" was GOOD, so that worked.   
 +  
 +TO CREATE TABLES that does not 
 +    $g_db = ADONewConnection($f_db_type); 
 +    $t_result = @$g_db->Connect($f_hostname, $f_db_username, $f_db_password, $f_database_name); 
 +  
 +The f_db_type is db2 for both.  Then I tried using the SAME id and pw: 
 +    $t_result = @$g_db->Connect($f_hostname, $f_admin_username, $f_admin_password, $f_database_name); 
 + 
 +And that does not work either.  Then I tried 
 +    $t_result = @$g_db->Connect($f_hostname, $f_admin_username, $f_admin_password); 
 + 
 +And that does not work either.  A debug statement I inserted shows:  
 +    Database user doesn't have access to the database ( ) HOST[S1071FDD] ID[PHP_IRA] PW[123123123] DB[MANTIS400] DBTYPE[db2] 
 +  
 +Makes no sense as the [] parms are correct.  This does NOT appear to be an MD5 issue at all. (pw masked with 123123123)  I removed the @ sign from the connect() and got no additional error info.  In fact, the parens on the output screen are empty. 
 +  
 + 
 +==== B. MD5 missing ==== 
 + 
 +Enabled mcrypt/mhash in the PHP extensions, and bounced.  That did NOT eliminate the MD5 warning.   
 +  "Checking for MD5 Crypt() support POSSIBLE PROBLEM - password security may be lower than expected"  
 +I had this with the MySQL install also! 
 + 
 + 
 +==== C. db2_tables error ==== 
 + 
 +Install.php ERROR:\\  
 +SYSTEM WARNING: db2_tables() expects parameter 1 to be resource, boolean given 
 +  
 +comes from FILE:\\  
 +/www/zendcore/htdocs/md/core/adodb/drivers/adodb-db2.inc.php and is complaining that the value of this->connection is null. 
 + 
 +  function &MetaTables($ttype=false) 
 +  { 
 +  global $ADODB_FETCH_MODE; 
 +  $savem = $ADODB_FETCH_MODE; 
 +  $ADODB_FETCH_MODE = ADODB_FETCH_NUM; 
 +  $qid = db2_tables($this->_connectionID); 
 + 
 +I cannot figure this out and do not know if it affects issue A. 
 + 
 +==== D. Creating SQL database manually ==== 
 + 
 +1. Run the install.php to generate the SQL by checking the box.  Copy and paste into a PC file editor. 
 + 
 +2. Removed formatting spaces to compact, as the SQL parser on the AS/400 has a length limit.  I try to keep the lines below 88 bytes. 
 + 
 +3. Split any lines that exceeded 88.  There are just a few. 
 + 
 +4. Add the required qualifier to tell DB2/400 WHERE to put the tables.  Prefix all table and index names with xxxx/ where xxxx is the library name that you designate in the "Database name" field in the install.php input screen.  "CREATE TABLE mantis_user_table" becomes "CREATE TABLE mantis011/mantis_user_table", for instance. 
 + 
 +5. Fix the error in the SQL generated: 
 + 
 + 
 + 365 CREATE TABLE mantis011/mantis_user_table ( 
 + ... 
 + 371 date_created TIMESTAMP DEFAULT '1970-01-01 00:00:01' NOT NULL, 
 + 372 last_visit TIMESTAMP DEFAULT '1970-01-01 00:00:01' NOT NULL, 
 + ... 
 + 380  PRIMARY KEY (id) 
 + 381 ); 
 + ERROR:  Timestamp does not match INSERT\\  
 + 395 INSERT INTO mantis_user_table(username, realname, email, password, date_created, 
 + ... 
 + 399 '2007-02-06, 09:10:36PM', '2007-02-06, 09:10:36PM', 1, 0, 90, 3, 0, 0, 
 + 400 'b4f45b80260a3ce540d14a897560ab9eed40d29997c90d4c63cda6ef153afb52'); 
 + 
 +THIS:\\  
 +  399 '2007-02-06, 09:10:36PM', '2007-02-06, 09:10:36PM', 1, 0, 90, 3, 0, 0, 
 +MUST BE:\\  
 +  399 '2007-02-06 09:10:36', '2007-02-06 09:10:36', 1, 0, 90, 3, 0, 0, 
 + 
 +6. Save the file as MANTISSQL on the PC 
 + 
 +7. Create a Source Physical File on the AS/400 
 + 
 + 
 +                      Create Source Physical File (CRTSRCPF) 
 + Type choices, press Enter. 
 + File . . . . . . . . . . . . . . > MANTISSQL     Name 
 +    Library  . . . . . . . . . . . >   MANTIS011   Name, *CURLIB 
 + Record length  . . . . . . . . . > 300           Number 
 + Member, if desired . . . . . . .   *NONE         Name, *NONE, *FILE 
 + Text 'description' . . . . . . .   Mantis SQL installation script 
 + 
 +  CRTSRCPF FILE(MANTIS011/MANTISSQL) RCDLEN(300)TEXT('Mantis SQL installation script'
 + 
 +8. Add the working LIBRARY to your library list:\\  
 +  addlible  mantis011 
 + 
 +9. FTP the mantissql pc file tp MANTIS011/mantissql  SRCPF 
 + 
 +  230 ICHANDLER logged on. 
 +  ftp> cd mantis011 
 +  250 "MANTIS011" is current library. 
 +  ftp> lcd md 
 +  Local directory now W:\LIVE\mantis-sql\md. 
 +  ftp> pwd 
 +  257 "MANTIS011" is current library. 
 +  ftp> lcd 
 +  Local directory now W:\LIVE\mantis-sql. 
 +  ftp> lcd md 
 +  Local directory now W:\LIVE\mantis-sql\md. 
 +  ftp> put mantissql 
 +  200 PORT subcommand request successful. 
 +  150 Sending file to member MANTISSQL in file MANTISSQL in library MANTIS011. 
 +  226 File transfer completed successfully. 
 +  ftp: 17753 bytes sent in 0.00Seconds 17753000.00Kbytes/sec. 
 + 
 +10. Once the file is in the source file on the AS/400, execute it by the Run SQL Statement command, shown prompted with F4: 
 + 
 +                         Run SQL Statements (RUNSQLSTM) 
 + Type choices, press Enter. 
 + Source file  . . . . . . . . . . > MANTISSQL     Name 
 +   Library  . . . . . . . . . . . >   MANTIS011   Name, *LIBL 
 + Source member  . . . . . . . . . > MANTISSQL     Name 
 + Commitment control . . . . . . . > *ALL          *CHG, *UR, 
 + Naming . . . . . . . . . . . . .   *SYS          *SYS, *SQL
  
 +And below in command line format:
  
 +  RUNSQLSTM SRCFILE(MANTIS011/MANTISSQL) SRCMBR(MANTISSQL) COMMIT(*ALL)
  
-http://wiki.splitbrain.org/wiki:syntax+11Congratulations.
  
mantisbt/systemi.1170355231.txt.gz · Last modified: 2008/10/29 04:32 (external edit)

Driven by DokuWiki