• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Server package...

Ricardo Paz

Reputable Poster
Hi list:
I'm trying to build a FULL Server package for CRP...everything seems to be
ok, but when the built finish, the PDF file displays a "Build Submitted"
status.
When checking the package built history, all BSFN show a NOT BUILT status,
and there are no objects to display...

I'll apreciate any help about it...


OW 73.3.2 SP 10.1 / NT 4.0 / SQL 7.0

Greetings.
S.E. Ricardo Paz Castañón
Systems Chief
Comercial de Herramientas S.a de C.v.
+52(8)369-35-35
rpaz@cohesa.com.mx
www.cohesa.com



Lic. Ricardo Paz Castanon
Jefe Sistemas COHESA
 

Ricardo Paz

Reputable Poster
Noop, my language profile is set to english, but I'm trying to build the
package for Domestic Language (english) and Spanish...

OW 73.3.2 SP 10.1 / NT 4.0 / SQL 7.0

Greetings.
S.E. Ricardo Paz Castañón
Systems Chief
Comercial de Herramientas S.a de C.v.
+52(8)369-35-35
rpaz@cohesa.com.mx
www.cohesa.com


-----Mensaje original-

Lic. Ricardo Paz Castanon
Jefe Sistemas COHESA
 

loriw

Active Member
I have had a similar problem when I re-use a package name. If I use a brand
new name for the package it seems to clear up the problem.

Lori Waybright
Inland Empire Paper Co.
509-924-1911

B733.2 - SP 10.1 - SQL 7.0 - NT 4.0 - Optio
 
When you build a server package, the following major events occur.

1. You packed all the runtime specs (*.ddb, *.xdb) when the R9621 ran on the Deployment Server. These packed or compressed spec's get put into the following folder when R9622 runs...

\\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\pack

2. The source and include c files and header files (includes NER's and TER's) get dropped into the following folders...

\\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\source\*.c
\\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\include\*.hxx

They get compiled and linked by the c compiler to create libraries of functions that get stored in the following folder

\\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\bin32\

Step 1 seems to be working for you. To check this, verify that files are getting dropped into the following folder....

\\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\spec

Also, ensure that the \\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\pack folder is empty.

Step 2 is where the c compiler compiles the code, and this is what is failing. Usually Build submitted means that the compiler is either incorrectly configured, or the JDE.INI file on the Enterprise Server isn't pointed to the compiler.

Here are the things to check.....

1. In the JDE.INI (or INI on the 400), check the following section...

[BSFN BUILD]

ON INTEL/NT

BuildArea=f:\jdedwardsoneworld\ddp\b7333\packages

where the path and drive letter listed point to where your packages folder is. If this is wrong, you will see build submitted since the compiler can't find the folder where the c files and h file are to compile and link.

Also check your environment variables for the compiler are setup at the SYSTEM level, and not the USER level on the Enterprise Server. Microsoft VC++ sets up these variables at the USER level, which means only the user who installed the compiler can run it. If they aren't at the system level, copy them from the user level to the system level. Without this, the compiler can't be found. If this occurs, you will see errors in the \\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\CompileLogs\*.log saying things like "This command is not recognized as an internal .... blah blah blah."

ON THE AS/400

BuildArea=/OneWorld/packages

where the library listed point to where your packages folder is. If this is wrong, you will see build submitted since the compiler can't find the folder where the c files and h file are to compile and link.

Also, make sure you have software options 13 & 15, since they are required by JDE for the compiler to work in OneWorld.

ON UNIX

BuildArea=/packages

again, just like above.


Also, try building an update package with just a few BSFN's in it. Then, when finished, look the the following logs for more information...

\\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\CompileLogs\*.log for the compiler logs.

\\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\text\*.sts status files for the BSFN's you are trying to build.

Hope this helps....

David McIlmoyl
CNC Consultant
Cain & Associates - Canadian JDE Business Partner of the Year
Email: David_McIlmoyl@cain-associates.com
 

Ricardo Paz

Reputable Poster
Thank´s David, I´ve checked all this things but there´s no way I can make it
work. the .sts files show a Waiting status, the bin32 and lib32 on the
enterprise are empty but the include and the source folder aren´t

-----Mensaje original-----
De: DavidMcIlmoyl [mailto:david_mcIlmoyl@cain-associates.com]
Enviado el: Martes 3 de Abril de 2001 6:01 PM
Para: jdelistml@jdelist.com
Asunto: Re: Server package...


When you build a server package, the following major events occur.

1. You packed all the runtime specs (*.ddb, *.xdb) when the R9621 ran on
the Deployment Server. These packed or compressed spec's get put into the
following folder when R9622 runs...

\\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\pack

2. The source and include c files and header files (includes NER's and
TER's) get dropped into the following folders...

\\{enterprise
server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\source\*.c
\\{enterprise
server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\include\*.hxx

They get compiled and linked by the c compiler to create libraries of
functions that get stored in the following folder

\\{enterprise
server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\bin32\

Step 1 seems to be working for you. To check this, verify that files are
getting dropped into the following folder....

\\{enterprise server}\jdedwardsoneworld\ddp\b733x\package\spec

Also, ensure that the \\{enterprise
server}\jdedwardsoneworld\ddp\b733x\package\pack folder is empty.

Step 2 is where the c compiler compiles the code, and this is what is
failing. Usually Build submitted means that the compiler is either
incorrectly configured, or the JDE.INI file on the Enterprise Server isn't
pointed to the compiler.

Here are the things to check.....

1. In the JDE.INI (or INI on the 400), check the following section...

[BSFN BUILD]

ON INTEL/NT

BuildArea=f:\jdedwardsoneworld\ddp\b7333\packages

where the path and drive letter listed point to where your packages folder
is. If this is wrong, you will see build submitted since the compiler can't
find the folder where the c files and h file are to compile and link.

Also check your environment variables for the compiler are setup at the
SYSTEM level, and not the USER level on the Enterprise Server. Microsoft
VC++ sets up these variables at the USER level, which means only the user
who installed the compiler can run it. If they aren't at the system level,
copy them from the user level to the system level. Without this, the
compiler can't be found. If this occurs, you will see errors in the
\\{enterprise
server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\CompileLogs\*.log
saying things like "This command is not recognized as an internal .... blah
blah blah."

ON THE AS/400

BuildArea=/OneWorld/packages

where the library listed point to where your packages folder is. If this is
wrong, you will see build submitted since the compiler can't find the folder
where the c files and h file are to compile and link.

Also, make sure you have software options 13 & 15, since they are required
by JDE for the compiler to work in OneWorld.

ON UNIX

BuildArea=/packages

again, just like above.


Also, try building an update package with just a few BSFN's in it. Then,
when finished, look the the following logs for more information...

\\{enterprise
server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\CompileLogs\*.log
for the compiler logs.

\\{enterprise
server}\jdedwardsoneworld\ddp\b733x\package\{packagename}\text\*.sts status
files for the BSFN's you are trying to build.

Hope this helps....

David McIlmoyl
CNC Consultant
Cain & Associates - Canadian JDE Business Partner of the Year
Email: David_McIlmoyl@cain-associates.com


--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=8
505


Lic. Ricardo Paz Castanon
Jefe Sistemas COHESA
 
Top