Web version | Full Versions | versions created on Web bulk management

 

They have been around for quite some time, but it's nice to have a refresher on these types of things.

8.12 and 9.0 have have started the functionality of these full versions, thank goodness - nobody enjoyed having to generate versions to convert them the fat versions and then manage the SDLC, although I believe that there is still something missing here.

Essentially when you create or change a "full version", the following places also get the changes:

1. Central Objects
2. F983051 Version List Master Entry
3. Serialized Object Tables
4. Server Package Specs.

So, I need more detail!

1. Central objects

So It probably only updates the RDASPEC for data selection and sequencing for the UBE (as version overrides are still FAT client only).  Now that is cool, is that a clayton’s checkin?  The check in that is not a check in… Or my other nerdy analogy, is this like vocab overrides (what do you mean your updating central objects without me hitting check in!!!!).

 

2. Easy, F983051

– processing options.

 

3. F989999 and F989998

This is great, this means that everyone can see the version and change it and run it straight away for that pathcode.

 

3.  Server Package Specs

So, the package that is deployed on the server is essentially a copy of central objects “at a point in time”.  So, this does the same as step 1, but alters the F98761DVBF40424 (or equivalent) for the currently deployed package.

So that all makes sense, what about OMW?  What about security for other people to change it, what about your SDLC?

· The web engine automatically does a submit specs, that is nice.  But what about the scheduler?  The specs will be read from the deployed full package, so that should be fine also

· SDLC is hit and miss, you need to manage them like BV’s.  So if people have been creating a bunch of them in PD, you might need to create a project and bring them into the SDLC, something like this will help you a lot (see insert statement down the page): 

· Note that an “install specs” is different to what it used to be, now an install specs updates the specs in the currently deployed package, which circumvents the need to build a package for a new version.  The scheduler will pick up these too.  That is nice.

Just created this, PY web.

Nothing goes to my default project either – which is interesting

 

How Can I identify these easily?

Maybe you can’t!  Sure you can write something like this, pretty much saying give me the version in PY, that are not in DV or UA and are also not in a project (and are not standard), this is probably the full list of versions that are web only in the PY environment.

select * from py910.f983051 t1

where not exists

(select 1 from sy910.f98222@e1sys

where POOMWOBJID = rtrim(ltrim(vrpid))||'|'||rtrim(ltrim(vrvers)))

and t1.vrvers not like 'ZJDE%' and t1.vrvers not like 'XJDE%'

and not exists (select 1

from ua910.f983051 t2

where t2.vrvers = t1.vrvers

and t2.vrpid = t1.vrpid)

and not exists (select 1

from dv910.f983051 t3

where t3.vrvers = t1.vrvers

and t3.vrpid = t1.vrpid);

Wow, that is 500+ for me.   This project is going to save me a lot of time.

Create a project called 'FullVersionsForSDLC', move it up to 26 and then bang out this SQL statement.

…and…

INSERT INTO SY910.F98222@e1sys (POOMWPRJID, POOMWOBJID, POOMWOT, POSRCRLS, POOMWUSER, POOMWMKEY, POENHV, POPATHCD, PODATS, POOMWCHS, POOMWOST, POOMWOVS, POOMWOBSDT, POOMWCRTDT, POOMWAC, POOMWTC, POOMWTCV, POOMWPOS1, POOMWPOS2, POOMWPOS3, POOMWPOS4, POOMWPOS5, POOMWPOD1, POOMWPOD2, POOMWPOD3, POOMWPOD4, POOMWPOD5, POOMWPON1, POOMWPON2, POOMWPON3, POOMWPON4, POOMWPON5, POPID, POMKEY, POUSER, POUPMJ, POUPMT, POTIMEZONES, PODSAVNAME)

SELECT 'FullVersionsForSDLC', rtrim(ltrim(vrpid))|| '|' ||rtrim(ltrim(vrvers)) , 'UBEVER' ,'E910','JDE','VSYDJDE02','PY910','PY910',' ','0','01',' ',0,0,' ',' ',' ','0',' ',' ',' ',' ',0,0,0,0,0,0.000000,0.000000,0.000000,0.000000,0.000000,'P98220','DSBSLSMOIRS','MOIRS',104303,143243.000000,' ',' '

from py910.f983051 t1

where vrpid like 'R%'

and not exists

(select 1 from sy910.f98222@e1sys

where POOMWOBJID = rtrim(ltrim(vrpid))||'|'||rtrim(ltrim(vrvers)))

and t1.vrvers not like 'ZJDE%' and t1.vrvers not like 'XJDE%'

and not exists (select 1

from ua910.f983051 t2

where t2.vrvers = t1.vrvers

and t2.vrpid = t1.vrpid)

and not exists (select 1

from dv910.f983051 t3

where t3.vrvers = t1.vrvers

and t3.vrpid = t1.vrpid);

570 rows inserted.

Commit;

What!! I just populated a project with the 500+ versions that have been created on the web!!! What, you can now promote this and synchronise all of your pathcodes… Today is a good day.

Great…  check in, check out and move up or down!