Web Only Version Pain

We seem to be having an issue with old “web only” versions.  There are times when the “web only” version causes the other version to not egen correctly.  So, below is the SQL that can be used to select the “web only” versions.

SELECT count(*) FROM COPD811/F983051
WHERE VRVCC2='1'             

If you want to be more precise, you can grab the “web only” versions that have been executed prior to a certain date by using the VRVED field and the six digit date which can be found on the e1 dates page.

Backup All SQL Server Databases

I came across this script to backup all SQL Server databases:

DECLARE @name VARCHAR(50) -- database name
DECLARE @path VARCHAR(256) -- path for backup files
DECLARE @fileName VARCHAR(256) -- filename for backup
DECLARE @fileDate VARCHAR(20) -- used for file name

SET @path = 'E:\Backups\Dynamics' 

SELECT @fileDate = CONVERT(VARCHAR(20),GETDATE(),112)

DECLARE db_cursor CURSOR FOR
SELECT name
FROM master.dbo.sysdatabases
WHERE name NOT IN ('master','model','msdb','tempdb') 

OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @name  

WHILE @@FETCH_STATUS = 0
BEGIN
       SET @fileName = @path + @name + '_' + @fileDate + '.BAK'
       BACKUP DATABASE @name TO DISK = @fileName 

       FETCH NEXT FROM db_cursor INTO @name
END  

CLOSE db_cursor
DEALLOCATE db_cursor

How To Find EnterpriseOne Web Only Versions

Dealing with EnterpriseOne “Web Only” versions can be a real pain.

They are deleted with each full package deployment and can cause a lot of confusion for the users.

In order to find these troublesome quasi-objects you can run the sql below:

Add Record To OCM – F986101

The other day, I had a need to insert many records into the OCM (F986101).  So I set out to create a quick SQL statement that would serve that purpose.  Below is what I came up with:

INSERT INTO SY811/F986101                         

VALUES('DV811',0,'OBJECTNAME','LOCAL','','*PUBLIC',  

'*ALL','P','','H95','AV','SQL','BSFN',            

'USERNAME','','','',0,'',0,'','','','')            

Remember � you may have to make entries in both the SY811 and SVM811 F986101 files.

Access To Environments

To find out what users or groups have access to a certain environment run the following SQL:

select * from sy811/f0093
where llll='<enviornment>'    

To find out what environments a user or group has access to run the following SQL:

select * from sy811/f0093
where lluser='<userid>'    

Clean Up Your Web-Only Versions

We have been having some issues lately where users create web-only versions and expect to use them after a full package has been built and deployed.

We have processes in place for them to submit new versions to our development teams, but sometimes things don�t happen the way they are designed.

Anyway, I was doing some checking and noticed that there were quite a few versions in the F983051 that were web-only versions and were older than the last full build.

So, I created an SQL that we are going to run immediately after the deployment of a new full package.

DELETE FROM <central objects>/F983051
WHERE VRVCC2='1'  

***NOTE: the syntax used in the SQL statement is for the IBM System i (as400, iSeries)

Egen Process JDBJ Gotcha

When setting up a workstation to perform the eGen process, once in a while there is a step that I seem to forget.  It has to do with two settings in the JDBJ.INI file that need to be changed from their default values and JDBJ driver files:

• [JDBj-SPEC DATA SOURCE] � This whole stanza needs to be commented out.  If you don�t, the eGen application will here for the location to which you want to generate your serialized objects, which is defaulted to the local MSDE database.
• [JDBj-JDBC DRIVERS] � The values in this stanza are commented out by default.  You will need to uncomment the drivers that are appropriate to your installation.  For me, that is:
• AS400=com.ibm.as400.access.AS400JDBCDriver
• SQLSERVER=com.microsoft.jdbc.sqlserver.SQLServerDriver
• JDBJ Driver Files � The four files below need to be copied to the C:\e811\MISC directory. 
• jt400.jar
• msbase.jar
• mssqlserver.jar
• msutil.jar

NOTE: This information is for Tools Release 8.97 and may be different for other versions.

Multi Threaded Kernel Issue When Upgrading To EnterpriseOne Tools Release 8.97.2.0

We ran into an issue when upgrading our EnterpriseOne Tools Release from 8.96.1.5 to 8.97.2.0. 

In order for the multi-threaded kernels to run correctly there is a setting in the JDE.INI file that needs to be set, SQLServerMode.

The error that I was getting was like the following:

ConnectDB:Unable to connect to DS ‘XXXXXXX – 811 Server Map’ in DB ‘XXXXXXX – 811 Server Map’ on Server DB ‘XXXXXXX’ via ‘L’ with Commitment ‘N’.

The solution indicated by Global Support was not available to me but the number is 201075487.  Below is the solution text that he sent:

On the Enterprise Server AS/400 JDE.INI, in the [DB SYSTEM SETTINGS] stanza, there is a default setting: SQLServerMode=N. 

For Multi Threaded Kernels to start and work, this setting needs to be Active or set to Y.  After adding the line to the stanza and setting it to Y, the customer was able to use Multi Threaded Kernels and the error disappeared.

I was unable to find the setting in Server Manager.

So, if you can find it, let me know.

Quick EnterpriseOne Version Security Solution

Whether you are trying to change the processing options of an interactive version or a batch version.  Sometimes you can run into issues where the application indicates that you do not have authority to change the version like the example to the left.

To quickly get around this error, we can use SQL to change the security setting in the F983051.

UPDATE CODV811/F983051
SET VREXCL = 0
WHERE vRPID = 'P03B2002'
AND VRVERS = 'TEST0001' 

Time To Change Your Password

We have our passwords set to expire every 90 days.

Sometimes there are user IDs that you don’t want to change but don’t really want them to show up on the audit report as not having an expiration period.

Here is a SQL statement that can help you:

UPDATE SY811/F98OWSEC
SET SCSECLST=<numeric date>
WHERE SCUSER='<UserID>' 

Next Page »