This INTEGER attaches one scheduler node underneath another in the hierarchical scheduling tree, so traffic scheduled at this node is itself subject to further arbitration at whatever scheduler this ID points to. Changing it effectively moves this whole scheduler subtree to compete under a different parent policy. A ParentSchedId pointing this scheduler beneath the port's root scheduler profile, for example, makes it compete fairly with sibling schedulers for the physical port's total capacity.