Wiki

User Tools

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

Site Tools

Trace:
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/07 00:04] – 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 227: Line 227:
 Issues of concern 2007-02-06 Issues of concern 2007-02-06
  
-==== A. /www/zendcore/htdocs/md/admin/install.php ====+==== A. install.php user error ====
  
 === NOTE: /www/zendcore/htdocs/md/config_inc.php should NOT exist prior to running install.php. === === NOTE: /www/zendcore/htdocs/md/config_inc.php should NOT exist prior to running install.php. ===
  
-Install.php will not work.  When run with the following parms (fields only in order): +/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 +
-## use proper pw of 10 char. below  +
-123123123      +
-## 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 +
-## use proper pw of 10 char. below  +
-123123123 +
-## box below is unchecked +
-[ ] Print SQL... +
-## then click +
-[Install...] +
  
 +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: 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:
Line 277: Line 273:
    
  
-==== B. /www/zendcore/htdocs/md/admin/install.php ====+==== B. MD5 missing ====
  
 Enabled mcrypt/mhash in the PHP extensions, and bounced.  That did NOT eliminate the MD5 warning.   Enabled mcrypt/mhash in the PHP extensions, and bounced.  That did NOT eliminate the MD5 warning.  
Line 284: Line 280:
  
  
-==== C. /www/zendcore/htdocs/md/core/adodb/drivers/adodb-db2.inc.php  ==== +==== C. db2_tables error ==== 
-ERROR:+ 
 +Install.php ERROR:\\ 
 SYSTEM WARNING: db2_tables() expects parameter 1 to be resource, boolean given SYSTEM WARNING: db2_tables() expects parameter 1 to be resource, boolean given
    
-comes from FILE: ../core/adodb/drivers/adodb-db2.inc.php and is complaining that the value of this->connection is null. +comes from FILE:\\  
- function &MetaTables($ttype=false) +/www/zendcore/htdocs/md/core/adodb/drivers/adodb-db2.inc.php and is complaining that the value of this->connection is null. 
- { + 
- global $ADODB_FETCH_MODE;+  function &MetaTables($ttype=false) 
 +  { 
 +  global $ADODB_FETCH_MODE;
   $savem = $ADODB_FETCH_MODE;   $savem = $ADODB_FETCH_MODE;
   $ADODB_FETCH_MODE = ADODB_FETCH_NUM;   $ADODB_FETCH_MODE = ADODB_FETCH_NUM;
Line 298: Line 297:
 I cannot figure this out and do not know if it affects issue A. I cannot figure this out and do not know if it affects issue A.
  
-==== D. Creating SQL database from statements ==== +==== D. Creating SQL database manually ==== 
-In order to get the database built, I ran the install.php to generate the SQL and captured it.+ 
 +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: 
  
-Pasted into a PC file editor.+ 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');
  
-Changed: +THIS:\\  
-1. 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. +  399 '2007-02-06, 09:10:36PM', '2007-02-06, 09:10:36PM', 1, 0, 90, 3, 0, 0, 
-2. Split any lines that exceeded 88.  There are just a few.+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)
  
 +11. Congratulations.
  
-http://wiki.splitbrain.org/wiki:syntax 
mantisbt/systemi.1170824679.txt.gz · Last modified: 2008/10/29 04:31 (external edit)
CC Attribution-Noncommercial-Share Alike 4.0 International Driven by DokuWiki