Results 1 to 2 of 2

Thread: 9.2 NER .h and .c at check-in

  1. #1
    Member
    Join Date
    Mar 2002
    Location
    Minneapolis, MN
    Posts
    783

    9.2 NER .h and .c at check-in

    Hey all,
    I am not very CNC literate. I am working on an upgrade to 9.2 (TR 9.2.4.1). In my past experience, I swear that checking-in NERs copies the local .h/.c files to their respective folders on the deployment server. Is that correct?

    What I am seeing is that is not the case. Is there anything in the OMW/CNC configuration that would dictate this? The c-BSFNs do copy the local .h/.c files just as expected (and necessary). I get that normally this is not a requirement for NERs as those files are generated automatically during package builds. Is this behavior just new to this release/TR?

    Just confused and wondering if anybody else has seen this or knows how to configure the system to force that copy.

    Thanks.
    Jeremy
    E1 Consultant
    Minneapolis, MN

  2. #2
    Source files are now located in the path codes respective Object Repository tables (F98780H and F98780R). During a check out, I believe it comes down from there, and checking in will put it back there. On a build, all of those objects are retrieved as part of the package for compile.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.